Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Improper CSRF token validation allows attackers to access victim's accounts linked to HackeroneAnalysed#1727221 | Valid | Cross-Site Request Forgery | – | 2023-06-19 | – | 168 |
| Slack integration setup lacks CSRF protection#170552 | Valid | Cross-Site Request Forgery | – | 2021-07-07 | $2,500 | 149 |
| Login CSRF vulnerability on hackerone.com#834366 | Valid | Cross-Site Request Forgery | – | 2020-06-12 | $500 | 84 |
| HackerOne reports escalation to JIRA is CSRF vulnerable#226418 | Valid | Cross-Site Request Forgery | – | 2017-08-30 | $500 | 36 |
| Information leakage via CSV when content is valid JavaScript#207266 | Valid | Cross-Site Request Forgery | – | 2017-05-23 | – | 29 |
| Switching the user to the attacker's account#727 | Valid | Cross-Site Request Forgery | – | 2014-02-20 | $150 | 27 |
| Information disclosure (reset password token) and changing the user's password#738 | Valid | Cross-Site Request Forgery | – | 2014-02-19 | $100 | 24 |
| CSRF login#547 | Valid | Cross-Site Request Forgery | – | 2014-01-13 | – | 24 |
| HackerOne is still prone to Internet Explorer UXSS#108056 | Informative | Cross-Site Request Forgery | – | 2017-04-19 | – | 23 |
| CSRF allows to test email forwarding#1131473 | Valid | Cross-Site Request Forgery | – | 2021-05-13 | – | 19 |
| Possible CSRF during joining report as participant#148517 | Valid | Cross-Site Request Forgery | – | 2016-07-12 | – | 18 |
| Possible CSRF during external programs#174470 | Valid | Cross-Site Request Forgery | – | 2016-10-18 | – | 12 |
| CSRF possible when SOP Bypass/UXSS is available#103787 | Valid | Cross-Site Request Forgery | – | 2015-12-30 | $2,500 | 11 |
| A password reset page does not properly validate the authenticity token at the server side.#742 | Valid | Cross-Site Request Forgery | – | 2014-04-19 | $100 | 11 |
| CSP Bypass: Click handler for links with data-method="post" can cause authenticity_token to be sent off domain#47472 | Valid | Cross-Site Request Forgery | – | 2015-02-26 | $2,000 | 10 |
| Limited CSRF bypass.#99708 | Valid | Cross-Site Request Forgery | – | 2015-12-02 | $500 | 9 |
| Websites opened from reports can change url of report page#124889 | Valid | Cross-Site Request Forgery | – | 2016-04-21 | – | 6 |
| Marking notifications as read CSRF bug#5946 | Valid | Cross-Site Request Forgery | – | 2015-04-28 | – | 4 |
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 (348 analysed so far), which can be wrong. Data as of 2026-11-14.