Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| User provided values passed to PHP unset() function#292500 | Informative | Memory Corruption | – | 2018-04-09 | – | 1 |
| User provided values trusted in sensitive actions#327867 | Informative | No weakness recorded | – | 2018-04-09 | – | 1 |
| Stored CSS InjectionAnalysed#315865 | Valid | Injection and Smuggling | – | 2018-04-02 | – | 15 |
| Prepopulation of email address and name leaks information provided to other merchantsAnalysed#316290 | Valid | Misconfiguration and Insecure Design | – | 2018-04-02 | – | 16 |
| ETH contract handling errorsAnalysed#328526 | Valid | Input Validation and Logic | Critical | 2018-04-04 | – | 208 |
| Ethereum account balance manipulationAnalysed#300748 | Valid | Input Validation and Logic | Critical | 2018-03-21 | – | 276 |
| Double Payout via PayPalAnalysed#307239 | Valid | Input Validation and Logic | Critical | 2018-04-04 | $10,000 | 324 |
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.