Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| 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 |
| Misconfigured SPF Record Flag#60260 | Informative | Misconfiguration and Insecure Design | – | 2016-02-22 | – | 3 |
| Content Spoofing in udemy#172711 | Valid | Misconfiguration and Insecure Design | Low | 2017-07-23 | – | 4 |
| Extremely high Course rating values could be set in order to make really high Average rating of the course. Negative values could be set to.#73808 | Valid | Misconfiguration and Insecure Design | – | 2015-09-25 | – | 5 |
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 (4,365 analysed so far), which can be wrong. Data as of 2026-11-15.