Dengage
Vulnerability disclosure program on security.txt dengage.com
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 6
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report by email
- [email protected]
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What the company's own policy page says it pays.
This program does not pay cash rewards.
- Pays cash
-
No
Dengage does not currently operate a paid bug bounty program.
- Safe harbor
-
Full
Dengage will not pursue legal action against researchers who conduct security research in good faith and comply with this policy.
- Hall of fame
-
Yes
Researchers who responsibly report valid vulnerabilities may be listed on our Security Acknowledgments page, subject to Dengage’s review and the researcher’s consent.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
6 assets you may test, 1 excluded.
Domains 5
- api.dengage.com
- app.dengage.com
- dengage.com
- panel.dengage.com
- trust.dengage.com
Products and areas 1
- Other Dengage-owned public web applications, APIs, and services
Out of scope (1)
- Systems, domains, or services not owned or operated by Dengage
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Dengage's policy.
While testing
-
Act in good faith and avoid harm to Dengage, its customers, and users.
-
Use only your own accounts or test accounts where possible.
-
Avoid accessing, modifying, deleting, exfiltrating, or disclosing customer, personal, or confidential data.
-
Avoid actions that may disrupt, degrade, or damage Dengage services.
-
Stop testing immediately and notify Dengage if you encounter sensitive data.
-
Keep vulnerability details confidential until Dengage has investigated and addressed the issue.
-
Comply with applicable laws and regulations.
-
Denial-of-service or resource exhaustion testing
-
Social engineering, phishing, spam, or physical attacks
-
Automated scanning that may affect service availability
Not accepted
-
Missing security headers without exploitable impact
-
SPF, DKIM, or DMARC configuration observations without demonstrated abuse
-
Clickjacking on pages without sensitive actions
-
Rate-limiting observations without practical abuse scenario
-
Self-XSS
-
Vulnerabilities requiring physical access to a user device
-
Issues in outdated browsers or unsupported platforms
-
Publicly available information or metadata
-
Best-practice recommendations without a concrete vulnerability
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 12 Nov 2026. Last checked 3 hours ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.