Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| xss on autoserch#61367 | Valid | Cross-site Scripting | – | 2015-07-08 | – | 1 |
| leak receipt of another user#61371 | Valid | Information Disclosure | – | 2015-11-13 | – | 2 |
| Multiple sub domain are vulnerable because of leaking full path#62778 | Valid | Information Disclosure | – | 2015-06-25 | – | 2 |
| xss profile#60016 | Valid | Cross-site Scripting | – | 2015-07-16 | – | 3 |
| XSS on https://www.udemy.com/asset/export.html#62400 | Valid | Cross-site Scripting | – | 2015-10-08 | – | 3 |
| XSS Vulnerability#87588 | Valid | Cross-site Scripting | – | 2015-11-09 | – | 3 |
| 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 |
| teach.udemy.com log poison vulnerability through wordpress debug.log being publically available#60058 | Valid | Command and Code Injection | – | 2015-06-09 | – | 8 |
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.