Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Udemy s3 storage can be used by an attacker personal website because of missing CSRF Token#172707 | Informative | Cross-Site Request Forgery | – | 2017-01-05 | – | 1 |
| CSRF Token Design Flaw#216161 | Informative | Cross-Site Request Forgery | None | 2017-08-28 | – | 1 |
| CSRF Token#257237 | Informative | Cross-Site Request Forgery | – | 2017-08-17 | – | 1 |
| Csrf on creating course#137008 | Informative | Cross-Site Request Forgery | – | 2017-01-10 | – | 3 |
| CSRF in Udemy.com#109839 | Informative | Cross-Site Request Forgery | – | 2017-01-10 | – | 11 |
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 (3,187 analysed so far), which can be wrong. Data as of 2026-11-15.