Details

No technology is perfect, and Weblate believes that working with skilled security researchers across the globe is crucial in identifying weaknesses in any technology. If you believe you've found a security issue in our product or service, we encourage you to notify us. We welcome working with you to resolve the issue promptly.

Disclosure Policy

Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.
Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.
Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
We're open in handling security issues, we will request public disclosure of all issues reported to us once they have been fixed.
All issues fixed by Git commits will reference corresponding HackerOne report with assumption that it will be publicly disclosed after fixing, so that third parties can verify the fix and original report.

Exclusions

While researching, we'd like to ask you to refrain from:

Denial of service
Spamming
Social engineering (including phishing) of Weblate staff or contractors
Any physical attempts against Weblate property or data centers
Please use the Sandbox translation project for testing

YOU MAY NOT TEST AGAINST SERVERS YOU DO NOT HAVE EXPLICIT PERMISSION TO TEST.

Scope

You are welcome to report issues in any part of our product, this includes:

Third parties

Please report vulnerabilities in third party products directly to them, here are some:

Known or intentional issues

Please avoid reporting following issues:

Text injection in error parameter while authenticating
Captcha weakness
We have intentionally enabled autocomplete for forms
There is a ssh honeypot running on some of our servers

Translations

Please note that Weblate is used for hosting third party translations, please do not report to us problems with these, but contact individual projects.

Thank you for helping keep Weblate and our users safe!

Disclosure Policy

Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.

Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.

Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.

We're open in handling security issues, we will request public disclosure of all issues reported to us once they have been fixed.

All issues fixed by Git commits will reference corresponding HackerOne report with assumption that it will be publicly disclosed after fixing, so that third parties can verify the fix and original report.

Exclusions

While researching, we'd like to ask you to refrain from:

Denial of service

Spamming

Social engineering (including phishing) of Weblate staff or contractors

Any physical attempts against Weblate property or data centers

Please use the Sandbox translation project for testing

YOU MAY NOT TEST AGAINST SERVERS YOU DO NOT HAVE EXPLICIT PERMISSION TO TEST.