Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| hosted.weblate.org: X-XSS-Protection not enabled#223396 | Valid | Cross-site Scripting | Low | 2017-05-17 | – | 2 |
| weblate.org: X-XSS-Protection not enabled#223723 | Valid | Cross-site Scripting | Low | 2017-05-17 | – | 2 |
| Self XSS at translation page through Editor Link at demo.weblate.org#223692 | Valid | Cross-site Scripting | Low | 2017-05-17 | – | 3 |
| [demo.weblate.org] Stored Self-XSS via Editor Link in Profile#223331 | Valid | Cross-site Scripting | Low | 2017-05-17 | – | 4 |
| Self-XSS can be achieved in the editor link using filter bypass#229735 | Valid | Cross-site Scripting | None | 2017-06-02 | – | 5 |
| Stored XSS @ /engage/<project_slug>#472391 | Valid | Cross-site Scripting | Medium | 2019-07-02 | – | 7 |
| Stored XSS via Create Project (Add new translation project)#610219 | Valid | Cross-site Scripting | Medium | 2019-07-09 | – | 11 |
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.