Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| CSRF Token Design Flaw#216161 | Informative | Cross-Site Request Forgery | None | 2017-08-28 | – | 1 |
| Weak Password#256663 | Informative | Misconfiguration and Insecure Design | None | 2017-08-28 | – | 1 |
| Violation of secure design principle#256665 | Informative | Misconfiguration and Insecure Design | None | 2017-08-17 | – | 1 |
| sweet32#217431 | Informative | Cryptography | None | 2017-05-04 | – | 2 |
| No password length restriction#258879 | Informative | Authentication | None | 2017-08-28 | – | 4 |
| Subdomain Takeover (and Stored XSS) via Trailing Dot at https://coding-exercises.udemy.comAnalysed#223625 | Valid | No weakness recorded | None | 2018-05-10 | – | 19 |
| S3 bucket unnecessarily discloses permissionsAnalysed#330135 | Valid | Access Control | None | 2019-04-26 | – | 27 |
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, where there is one, which can be wrong. Data as of 2026-11-15.