CVE-2025-47951: WeblateOrg weblate · Improper Restriction of Excessive Authentication Attempts
Affects WeblateOrg weblateSource CVE Database V5
Not known to be exploited · CVSS 4.9 Medium : upgrade to 5.12 when convenient.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.12
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade weblateorg/weblate to 5.12.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubweblateorg/weblatepkg:github/weblateorg/weblateOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Immediate Upgrade: Organizations should upgrade Weblate installations to version 5.12 or later, where the vulnerability is patched by implementing rate limiting on the 2FA verification endpoint.
- Credential Hygiene: Enforce strong password policies and monitor for credential leaks or reuse to reduce the risk of attackers obtaining valid credentials necessary to exploit this vulnerability.
- Enhanced Monitoring: Implement monitoring and alerting for unusual authentication patterns, such as repeated OTP verification attempts from the same IP or account, to detect brute force attempts early.
- Network Controls: Restrict access to Weblate administrative and authentication endpoints via IP whitelisting or VPNs where feasible, limiting exposure to potential attackers.
- Multi-Factor Authentication Alternatives: Consider deploying additional or alternative second factor methods that may be less susceptible to automated guessing, such as hardware tokens or push-based authentication, if supported.
- Incident Response Preparedness: Develop and test incident response plans that include steps for handling suspected account compromises in Weblate, including forced password resets and session invalidation.
- Application Layer Protections: If upgrading is delayed, implement external rate limiting or web application firewall (WAF) rules to throttle requests to the 2FA endpoint, mitigating brute force attempts at the network perimeter.
Description
Weblate is a web based localization tool. Prior to version 5.12, the verification of the second factor was not subject to rate limiting. The absence of rate limiting on the second factor endpoint allows an attacker with valid credentials to automate OTP guessing. This issue has been patched in version 5.12.
References
- github.com/WeblateOrg/weblate/security/advisories/GHSA-57jg-m997-cx3q (opens in a new tab)
- github.com/WeblateOrg/weblate/pull/14918 (opens in a new tab)
- github.com/WeblateOrg/weblate/commit/f806293451248c5d95e45b3b507e9d158bc4f384 (opens in a new tab)
- hackerone.com/reports/3150564 (opens in a new tab)
- github.com/WeblateOrg/weblate/releases/tag/weblate-5.12.1 (opens in a new tab)