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 | High | 2023-06-19 | – | 168 |
| Slack integration setup lacks CSRF protectionAnalysed#170552 | Valid | Cross-Site Request Forgery | High | 2021-07-07 | $2,500 | 149 |
| Login CSRF vulnerability on hackerone.comAnalysed#834366 | Valid | Cross-Site Request Forgery | Low | 2020-06-12 | $500 | 84 |
| Partial report contents leakage - via HTTP/2 concurrent stream handlingAnalysed#493176 | Valid | Information Disclosure | Medium | 2021-08-05 | $2,500 | 64 |
| Stored XSS on https://events.hackerone.comAnalysed#1028332 | Valid | Cross-site Scripting | None | 2021-03-26 | – | 59 |
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 (2,190 analysed so far), which can be wrong. Data as of 2026-11-15.