Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Bruteforce password recovery codeAnalysed#743545 | Valid | Misconfiguration and Insecure Design | – | 2020-01-18 | – | 258 |
| Leak of authorization urls leads to account takeoverAnalysed#746186 | Valid | Misconfiguration and Insecure Design | – | 2020-05-08 | – | 109 |
| On Singing up with a Phone number , The 4 digit OTP does not expires for a long time leading to an easy attack and make a verified account easiltyAnalysed#792295 | Valid | Misconfiguration and Insecure Design | High | 2020-11-25 | – | 49 |
| Email Spoofing#182467 | Valid | Misconfiguration and Insecure Design | Low | 2017-01-24 | – | 28 |
| crossdomain.xml too permissive on eu1.badoo.com, us1.badoo.com, etc.#96662 | Valid | Misconfiguration and Insecure Design | – | 2017-08-31 | – | 16 |
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,444 analysed so far), which can be wrong. Data as of 2026-11-15.