Weblate Vulnerability Disclosure Program

Program Overview

Weblate runs a vulnerability disclosure program on HackerOne. The program has 6 in-scope assets.

In-Scope Assets

Asset	Type	Max Severity	Eligible
hosted.weblate.org	URL	Critical	No Bounty
https://github.com/WeblateOrg/docker	SOURCE_CODE	Critical	No Bounty
https://github.com/WeblateOrg/translation-finder	SOURCE_CODE	Critical	No Bounty
https://github.com/WeblateOrg/weblate	SOURCE_CODE	Critical	No Bounty
https://github.com/WeblateOrg/website	SOURCE_CODE	Critical	No Bounty
https://github.com/WeblateOrg/wlc	SOURCE_CODE	Critical	No Bounty

Out-of-Scope Assets

• github.com
• hg.weblate.org

Tips for Hacking Weblate

1. Read the policy — Understand what's in scope, out of scope, and any specific testing restrictions before you start.
2. Enumerate the attack surface — Use subdomain enumeration and directory bruteforcing to map all accessible endpoints.
3. Focus on high-impact bugs — Look for SQL injection, SSRF, and IDOR vulnerabilities first.
4. Test authentication flows — Check for OAuth misconfigurations and CSRF in login/signup flows.
5. Write clear reports — Include steps to reproduce, impact assessment, and suggested remediation. Use Burp Suite to capture evidence.

Frequently Asked Questions

How do I start hacking Weblate?

Sign up on HackerOne, read the program policy carefully, review the in-scope assets listed above, and start testing. Always stay within scope and follow responsible disclosure guidelines.

Does Weblate pay bounties?

No, Weblate runs a Vulnerability Disclosure Program (VDP) without monetary rewards. You may receive recognition or swag.

What types of vulnerabilities does Weblate accept?

Weblate accepts reports for vulnerabilities found in their 6 in-scope assets. Common accepted vulnerability types include XSS, SQL injection, SSRF, IDOR, authentication bypass, and RCE. Check the program policy for specific exclusions.