Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Weak Email Verification: Newly Registered Users Can Bypass Email Verification Step and Log InAnalysed#2312320 | Valid | Authentication | Medium | 2024-01-19 | – | 48 |
| Unauthenticated File Upload to CDNAnalysed#3589247 | Valid | Access Control | Medium | 2026-05-18 | – | 56 |
| Revocation API Token by Bypassing The XSRF TokenAnalysed#2312217 | Valid | Cross-Site Request Forgery | Critical | 2024-01-19 | – | 60 |
| Unauthenticated GraphQL access by prepending __schema to private operationsAnalysed#3452015 | Valid | Authentication | Medium | 2025-12-05 | $500 | 76 |
Status and severity are HackerOne's. “Access stated” is what the title says; “Access needed” and techniques come from CyberSIXT's analysis of the public report (2,942 analysed so far), which can be wrong. Data as of 2026-11-15.