- Top reward
- $2,000
- Top severity paid
- Critical
- Assets in scope
- 6
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays up to $2,000
- for critical bugs.
- Report by email
- [email protected]
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 2 days
- As the policy promises.
- Paid by wire transfer
- No identity requirement stated.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What the company's own policy page says it pays.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$2,000 from $1,500 |
| High |
|
$1,000 from $750 |
| Medium |
|
$400 from $200 |
- Top reward
-
$2,000
Critical : 1500$ ~ 2000$
- Response
-
Within 2 days
First response time : 2-5 business days
- Safe harbor
-
Full
Superside will not engage in legal action against individuals who submit vulnerability reports through our Vulnerability Reporting inbox.
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, 3 excluded.
Web 5
- https://admin.supersidestaging.com
- https://api-internal.supersidestaging.com
- https://api.supersidestaging.com
- https://app.supersidestaging.com
- https://internal.supersidestaging.com
Domains 1
- supersidestaging.com
Out of scope (3)
- superside.com
- production environment
- *.superside.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Superside's policy.
While testing
-
Testing is prohibited on the production environment.
-
Researchers must not disclose or exploit any vulnerabilities found, except for the sole purpose of testing and reporting the vulnerability to Superside in terms of this policy.
-
If sensitive information, such as personal information, credentials, etc., is accessed as part of a vulnerability, it must not be saved, stored, transferred, accessed, or otherwise processed after initial discovery.
-
Researchers must not publicly disclose any vulnerabilities before Superside has had a reasonable opportunity to remediate them and without prior written consent.
-
Researchers must not access or attempt to access any data or systems that are not directly related to the vulnerability report.
-
Researchers must comply with all applicable laws and regulations, including data protection laws, when participating in the bug bounty program.
Not accepted
-
Denial of Service attacks
-
Descriptive error messages or headers (e.g. Stack Traces, banner grabbing)
-
Attacks requiring physical access to a user's device
-
Mail configuration issues including SPF, DKIM, DMARC settings
-
IDORs using UUIDs without a direct way to enumerate those UUIDs
-
EXIF metadata stripping related reports
-
Third-party applications and third-party APIs
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 11 Nov 2026. Last checked 6 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.