Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Hacker can bypass 2FA requirement and reporter blacklist through embedded submission formAnalysed#418767 | Valid | Access Control | Medium | 2018-10-31 | $10,000 | 208 |
| Bypassing HackerOne 2FA due to race conditionAnalysed#2598548 | Valid | Input Validation and Logic | Medium | 2024-10-30 | – | 139 |
| Password not checked when disabling 2FA on HackerOneAnalysed#587910 | Valid | Misconfiguration and Insecure Design | Low | 2019-06-07 | – | 95 |
| Changing the 2FA secret key and backup codes without knowing the 2FA OTPAnalysed#1139535 | Valid | Other weaknesses | Medium | 2021-05-06 | – | 57 |
| Pre-generation of 2FA secret/backup codes seems like an unnecessary riskAnalysed#100509 | Valid | No weakness recorded | – | 2015-12-02 | $1,000 | 15 |
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.