Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Insecure API Response Leads to Disclosure of Hashed PasswordsAnalysed#2788557 | Valid | Information Disclosure | Medium | 2024-11-26 | – | 61 |
| unauthorized access and add user and change personal information all usersAnalysed#2828641 | Valid | Access Control | Critical | 2025-05-27 | – | 54 |
| change part of personal information all usersAnalysed#2828693 | Valid | Access Control | Critical | 2025-05-12 | – | 53 |
| Publicly accessible `█████████` endpoint exposing internal user identifiers and email addressesAnalysed#3360293 | Valid | Information Disclosure | Medium | 2026-02-24 | – | 49 |
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.