Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Email SpoofingAnalysed#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 |
| Leave inaccessible messaging system with a message (https://us1.badoo.com)#178742 | Valid | No weakness recorded | Medium | 2017-01-19 | – | 10 |
| Arbitrary modification value "session" (Cookie) in badoo.com#178567 | Valid | No weakness recorded | Low | 2017-06-25 | – | 9 |
| Open redirect helps to steal Facebook access_token#99435 | Valid | Open Redirect | – | 2017-08-31 | – | 9 |
| CSRF bug#239170 | N/A | Cross-Site Request Forgery | – | 2017-06-12 | – | 6 |
| CSRF Attack on (m.badoo.com)deleting account and erasing imported contacts#192131 | Valid | Cross-Site Request Forgery | Medium | 2017-02-06 | $280 | 5 |
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 (3,935 analysed so far), which can be wrong. Data as of 2026-11-15.