Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as team member without 2FA
-
ExploitAccess global permission granted by team
-
ExecutionNavigate to /manage/ site interface
-
ImpactAct on site-wide management capabilities
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Access control enforcement
MITRE ATT&CK
1 technique across 1 tactic: Defense Evasion The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires three concurrent conditions: (1) the Weblate instance has at least one team with the enforced_2fa flag set to True; (2) that team has been granted a site-wide global permission (such as management.use); and (3) the exploiting user is a human member of that team who has not configured a two-factor authentication device. Bot users are explicitly exempt from the 2FA check by design and are not affected. The vulnerability does not apply to project-, component-, or workspace-scoped permissions, which were already correctly gated. Exploitation is further limited by the need for an attacker to already be an authenticated, team-assigned user - unauthenticated access is not possible. |
| Impact | The provided CVSS vector (AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N) scores 4.4 and reflects a moderate, network-accessible flaw requiring high privileges, which is broadly consistent with the description - the user must already be a member of a privileged team granted global permissions. However, PR:H warrants scrutiny: the attacker is a legitimate authenticated user placed into a team by an administrator, which arguably maps closer to PR:L than PR:H, since the user does not themselves need to hold administrative access prior to exploitation. EPSS data was not provided, and there is no CISA KEV listing, so no signals of active exploitation exist beyond the vendor's own disclosure. The realistic risk is narrow: it requires an administrator to have created a team with both enforced_2fa and a global permission grant, and a user in that team who hasn't yet enrolled a TOTP device. That combination is plausible in organizations transitioning to mandatory 2FA - a window during rollout where users are added to teams before completing enrollment. The actual impact, unauthorized access to the /manage/ interface, is significant for a Weblate instance managing sensitive translation workflows or internal tooling, but the constrained preconditions limit widespread exposure. |
| Exploit ScenarioDerived | An administrator creates a team named 'Site Managers' with enforced_2fa=True and grants it the global management.use permission, then adds a newly onboarded user to the team before that user completes 2FA enrollment. The user, without configuring a TOTP device, navigates to /manage/ and gains access to the site management interface, bypassing the intended 2FA gate entirely. No public exploit code exists; the flaw is exploitable by any authenticated user in this state using a standard browser. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 26, 2026
Global permission bypass in Weblate prior to 2026.7 allows authenticated team members to receive site-wide management permissions without satisfying their team's enforced two-factor authentication requirement. While 2FA enforcement was correctly applied to project-, component-, and workspace-scoped permissions, the same gate was absent for global permissions, meaning a user lacking a configured TOTP device could still access the site management interface at /manage/. No public exploit code is identified at time of analysis, and the issue is fixed in version 2026.7.
RemediationAI
Upgrade to Weblate 2026.7 or later, which contains the authoritative fix (commit 89042ab12268842655ddc10cb052bfc4dfa7a589). The patch modifies weblate/auth/models.py to exclude teams with enforced_2fa=True from the global permission queryset for users who have not configured a 2FA device. Until an upgrade is feasible, administrators can audit all teams that both enforce 2FA and hold global permissions and ensure no team members lack an active TOTP device; alternatively, temporarily remove global permissions from enforced-2FA teams and grant them only to fully-enrolled users through separate groups. Restricting network access to the /manage/ endpoint via reverse proxy rules (e.g., IP allowlist) is a compensating control that limits the blast radius of unauthorized access but does not address the underlying authorization defect. Full details and patch references are at https://github.com/WeblateOrg/weblate/security/advisories/GHSA-x86c-ff69-cr2m.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Weblate (CPE: cpe:2.3:a:weblateorg:weblate:*:*:*:*:*:*:*:*) is a Django-based web localization platform. Its access control model uses Groups with optional enforced_2fa flags; permissions are scoped to project, component, workspace, or global levels. The fix (commit 89042ab) reveals that the flaw resided in weblate/auth/models.py, where the queryset that resolves global team memberships for a user did not filter out teams with enforced_2fa=True when the user lacked a configured 2FA device. The corrected logic adds: if the user is not a bot and does not have 2FA configured, exclude any team with enforced_2fa=True before returning global permissions. CWE-284 (Improper Access Control) accurately describes the root cause - a policy check enforced at scoped permission resolution was simply absent at the global permission resolution path.
Know when Weblate gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N
PR:L over PR:H because the exploiter is a regular authenticated team member, not an administrator; I:L added since /manage/ access enables configuration changes beyond read-only.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
1DescriptionCVE.org
Weblate is a web-based continuous localization platform used to manage software translations. In versions prior to 2026.7, a team can require its members to configure two-factor authentication before receiving the team's permissions, but this requirement is not enforced for site-wide global permissions. As a result, a user who belongs to a team that enforces 2FA and grants a global permission still receives that global permission even without 2FA configured, while the same requirement is correctly applied to project-, component-, and workspace-scoped permissions. Such a user can act on the granted global permission, including reaching the site management interface at /manage/. This issue is fixed in version 2026.7.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Improper input validation in Weblate versions prior to 5.15.1 lets a user who can submit translation files or restore pr
Privilege escalation in Weblate versions prior to 5.17 allows an authenticated low-privileged user to modify sensitive f
The package weblate from 0 and before 4.11.1 are vulnerable to Remote Code Execution (RCE) via argument injection when u
Argument injection in Weblate's Mercurial backend lets an authenticated user with project-scoped component.edit permissi
Weblate's REST API failed to enforce permission scope on team (group) assignments in all versions prior to 2026.7, allow
Remote code execution in Weblate's project backup restoration affects versions prior to 5.17, exploitable by authenticat
The wlc Weblate command-line client prior to version 1.17.2 is vulnerable to arbitrary file write attacks through path t
Arbitrary file read via symlink traversal in Weblate's App store metadata ZIP download affects all versions prior to 202
Arbitrary file read vulnerability in Weblate versions prior to 5.17 allows authenticated attackers to read sensitive fil
Weblate versions prior to 5.15.2 expose screenshot images through the web server without authentication controls, enabli
Path traversal in Weblate allows authenticated users to read arbitrary files outside the repository via the translation
Weblate versions up to 5.16.0 contains a vulnerability that allows attackers to an argument injection to `ssh-add` (CVSS
EUVD-2026-66714
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB