Skip to content

Bug bounty reports15,219

Publicly disclosed HackerOne reports, with the platform's own outcome and severity.

Program:Weblate
Status
Severity:None
Clear
Weakness
Year
Bounty paid0
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
Technique
Clear filters28 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
DNSSEC Zone Walk using NSEC Records#228471InformativeInformation DisclosureNone2018-01-30–1
CSP "script-src" includes "unsafe-inline" in weblate.org and demo.weblate.org#231062InformativeMisconfiguration and Insecure DesignNone2017-05-23–1
No rate limit or captcha to identify humans#257384ValidMisconfiguration and Insecure DesignNone2017-09-15–1
Specify maximal length in translation#224015ValidMisconfiguration and Insecure DesignNone2017-05-17–2
Incorrect HTTPS Certificate#225540ValidCryptographyNone2017-06-16–2
Directory Listing#223384ValidCryptographyNone2017-06-16–3
HttpOnly Flag not set#224006ValidMisconfiguration and Insecure DesignNone2017-05-18–3
Improper validation of unicode characters#2#279945InformativeNo weakness recordedNone2020-07-26–3
hosted.weblate.org display of unfiltered results#1454552InformativeNo weakness recordedNone2022-01-21–3
Abuse of Api that causes spamming users and possible DOS due to missing rate limit on contact form#223542ValidNo weakness recordedNone2017-05-17–4
No filteration of null characters in name field#242945ValidMisconfiguration and Insecure DesignNone2017-07-27–4
Error Message When Changing Username#243664ValidInput Validation and LogicNone2017-08-17–4
Improper validation of unicode characters#278718ValidNo weakness recordedNone2017-11-17–4
Audit log validation#296632ValidInjection and SmugglingNone2018-08-28–4
Access to completion page without performing any action#223846ValidAccess ControlNone2017-05-18–5
Self-XSS can be achieved in the editor link using filter bypass#229735ValidCross-site ScriptingNone2017-06-02–5
Option method enabled#230194ValidMisconfiguration and Insecure DesignNone2017-05-21–5
The username of an account can be ..#243609ValidInput Validation and LogicNone2017-07-27–5
Password token validation in Weblate Bypass#243842ValidAuthenticationNone2017-08-21–5
Secret_key in GitHub#926093InformativeInformation DisclosureNone2020-07-18–6
Running 2 accounts with a single email#224072ValidInput Validation and LogicNone2017-05-18–7
Weblate |Security Misconfiguration| Method Enumeration Possible on domain#230648ValidNo weakness recordedNone2017-07-02–7
Missing Restriction On String Size#257376ValidMemory CorruptionNone2017-09-16–8
Missing filteration of meta characters in full name field on registration page https://demo.weblate.org/accounts/register#225901ValidMisconfiguration and Insecure DesignNone2017-05-22–9
DKIM records not present, Email Hijacking is possible.....#253926ValidAuthenticationNone2017-09-16–12
No rate limiting for Remove Account lead to huge Mass mailingsAnalysed#1723445ValidInput Validation and LogicNone2022-11-20–13
Broken Authentication – Session Token bugAnalysed#400826ValidNo weakness recordedNone2018-09-26–19
Open Github Repo Leaking WEBLATE SECRET KEYAnalysed#942146ValidCryptographyNone2020-07-26–22

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.