Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| **Unauthenticated IDOR allows modification of payment customer billing information**Analysed#3869124 | Valid | Insecure Direct Object Reference | High | 2026-08-30 | – | 72 |
| Unauthenticated ?q= search query causes exponential pyparsing backtracking under a process-global lock in WeblateAnalysed#3898281 | Valid | Denial of Service | High | 2026-09-04 | – | 33 |
| no captcha for register user and weak question attacker can spam emailAnalysed#236398 | Valid | Misconfiguration and Insecure Design | – | 2019-10-26 | – | 29 |
| Open Github Repo Leaking WEBLATE SECRET KEYAnalysed#942146 | Valid | Cryptography | None | 2020-07-26 | – | 22 |
| HTML injection and information disclosure in support panelAnalysed#634312 | Valid | Information Disclosure | Medium | 2019-07-09 | – | 20 |
| Rate Limit Bypass on login PageAnalysed#224460 | Valid | Authentication | Medium | 2017-05-17 | – | 18 |
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.