Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| HackerOne making payments in USDC (Coinbase stable coin)Analysed#1220747 | Valid | No weakness recorded | None | 2021-06-17 | – | 201 |
| Stored XSS on https://events.hackerone.comAnalysed#1028332 | Valid | Cross-site Scripting | None | 2021-03-26 | – | 59 |
| Updating payout preference to CurrencyCloud doesn't notify user via emailAnalysed#240083 | Valid | Misconfiguration and Insecure Design | None | 2018-01-31 | $500 | 35 |
| User object in GraphQL exposes number of trial reports for External Programs that also have a Private ProgramAnalysed#350964 | Valid | Information Disclosure | None | 2018-06-27 | – | 24 |
| Invalid Phabricator API token revealed through error message when escalating a reportAnalysed#335123 | Valid | Information Disclosure | None | 2018-06-27 | $500 | 18 |
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 (4,614 analysed so far), which can be wrong. Data as of 2026-11-15.