Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Adding or removing a new non-preferred payout method does not trigger an e-mail or account notificationAnalysed#242964 | Valid | Input Validation and Logic | Medium | 2017-11-01 | – | 46 |
| Report invitation links not restricted to any existing userAnalysed#214839 | Valid | Information Disclosure | Low | 2017-05-23 | $500 | 39 |
| HackerOne reports escalation to JIRA is CSRF vulnerableAnalysed#226418 | Valid | Cross-Site Request Forgery | Medium | 2017-08-30 | $500 | 36 |
| View Any Program's Team Members through GET https://hackerone.com/invitations/Analysed#283014 | Valid | Information Disclosure | Medium | 2017-11-01 | $1,000 | 32 |
| Additional bypass allows SSRF for internal netblocksAnalysed#288950 | Valid | Server-Side Request Forgery | – | 2017-11-16 | – | 20 |
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.