Weblate
Monthly
Argument injection in Weblate's Mercurial backend lets an authenticated user with project-scoped component.edit permission plant a dash-prefixed repository filename that Mercurial later interprets as a command-line option instead of a literal path, resulting in arbitrary command execution with the privileges of the Weblate service account when the repository is next updated. The issue affects Weblate 4.11.1 through 2026.7.1 and is a residual, incomplete fix for CVE-2022-23915; although it carries a CVSS of 8.5, exploitation requires a Mercurial-backed RESX component using the 'Update RESX files' add-on plus a subsequent repository update, so the realistic attack surface is narrow. A vendor patch is available in Weblate 2026.8, and no public exploit identified at time of analysis.
Arbitrary file read via symlink traversal in Weblate's App store metadata ZIP download affects all versions prior to 2026.7, allowing project administrators to exfiltrate host files outside their repository boundary. The vulnerability is an incomplete fix for CVE-2026-34242 - the original patch blocked path traversal via '..' sequences but failed to prevent symlink-based traversal, leaving the arbitrary file read primitive intact. No public exploit has been identified at time of analysis; the CVSS score of 7.7 High reflects scope change due to cross-boundary file disclosure, while the project-administrator privilege requirement limits the exploitable population.
Weblate's REST API failed to enforce permission scope on team (group) assignments in all versions prior to 2026.7, allowing any authenticated low-privilege user to assign unauthorized projects or workspaces to a team via the API. The root serializer field `defining_workspace` resolved primary keys against `Workspace.objects.all()` without filtering by the requesting user's permissions, enabling horizontal privilege escalation to private projects. Vendor-released patch 2026.7 is confirmed; no public exploit code or CISA KEV listing exists at time of analysis.
Privilege escalation in Weblate versions prior to 5.17 allows an authenticated low-privileged user to modify sensitive fields (like roles or permissions) of any user account through the REST API's user patching endpoint, leading to full system compromise. The vulnerability stems from insufficient field-level authorization, and the EPSS exploitation probability is very low (0.04%) with no known active exploitation; a vendor patch is available in version 5.17.
Arbitrary file read vulnerability in Weblate versions prior to 5.17 allows authenticated attackers to read sensitive files from the server via symlink traversal in the ZIP download feature. No active exploitation or public exploit code has been identified, and the EPSS score (0.01%) indicates very low likelihood of exploitation. A vendor-released patch is available in Weblate 5.17.
Remote code execution in Weblate's project backup restoration affects versions prior to 5.17, exploitable by authenticated users with project-creation privileges. Backup archives were extracted without filtering Git (`.git/config`, `.git/hooks/*`, `.git/modules/`) and Mercurial (`.hg/hgrc`) configuration files, allowing a crafted archive to plant malicious VCS hooks or rewrite repository configuration. When Weblate subsequently performs git operations on the restored component, attacker-supplied hook scripts execute with server-process privileges. No public exploit or active exploitation has been confirmed (SSVC: Exploitation none; EPSS 0.33%).
The wlc Weblate command-line client prior to version 1.17.2 is vulnerable to arbitrary file write attacks through path traversal when downloading multi-translations from a malicious or compromised server. An authenticated attacker can exploit this vulnerability by crafting a specially designed server response to write files to arbitrary locations on the victim's system, potentially compromising system integrity. This vulnerability affects wlc versions before 1.17.2 and is fixed in the patched version.
Weblate versions prior to 5.15.2 expose screenshot images through the web server without authentication controls, enabling unauthenticated attackers to retrieve sensitive screenshots by predicting their filenames. This improper access control flaw affects all users whose screenshot content should be restricted. A patch is available in version 5.15.2 and later.
DNS rebinding SSRF in Weblate prior to version 2026.8 allows an authenticated user with VCS component URL management privileges to circumvent VCS_RESTRICT_PRIVATE protections and reach internal network services. The attack exploits the time gap between Weblate's initial hostname validation and the VCS client's subsequent independent DNS lookup - an attacker-controlled domain passes validation pointing to a public IP, then switches to an internal address before the actual VCS connection is made. Triggering a clone, fetch, push, or similar operation then causes Weblate to connect to internal VCS-compatible services and potentially expose their contents. No public exploit has been identified at time of analysis, though the DNS rebinding technique is well-understood and toolkits for it exist.
Object-scoped RSS feeds in Weblate prior to version 2026.8 bypass the platform's permission model, exposing change-history metadata from private projects and restricted components to any requester - including unauthenticated users on installations that permit anonymous access. The exposed metadata includes project and component identities, contributor usernames and full names, action types, timestamps, and translation unit links, enabling enumeration of contributor identity and project structure in otherwise-private deployments. No public exploit has been identified at time of analysis and this vulnerability is not listed in CISA KEV, but the lack of any exploitation prerequisite on anonymously accessible instances makes it straightforward to abuse with standard HTTP tooling.
Unbounded regular expression evaluation in Weblate prior to 2026.7 allows any authenticated user holding the built-in 'Edit source' role to induce sustained CPU exhaustion by storing a catastrophically-backtracking pattern in a source string's quality-check flags. Both the RegexCheck and PlaceholderCheck mechanisms compile user-supplied expressions at validation time but execute them without any runtime timeout, so a single malicious flag edit can pin server CPU indefinitely by re-triggering evaluation across every linked translation unit in the same request. No public exploit code exists and the issue is not listed in CISA KEV, but the low complexity and clear role-based attack path make it a credible internal or supply-chain threat for multi-contributor Weblate deployments.
Nested API change endpoints in Weblate prior to version 2026.7 bypass component-level access controls, exposing change history of restricted components to authenticated project members who lack direct view permissions. A low-privileged project member can call the project-, component-, or translation-level change list endpoints to enumerate change records for restricted components - including source and translated string content, component identity, and change metadata - that return 404 on direct component access. No public exploit or CISA KEV listing has been identified; real-world risk is conditional on use of Weblate's restricted component feature.
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.
Object existence enumeration in Weblate prior to version 2026.7 allows authenticated low-privilege users to infer whether objects exist within private projects by observing differential HTTP response codes - HTTP 403 (Forbidden) for existing-but-inaccessible objects versus HTTP 404 (Not Found) for truly absent ones. Affected endpoints performing globally-scoped ORM lookups across changes, comments, and announcements fail to restrict results to projects the requesting user is authorized to view. No public exploit has been identified and this is not listed in CISA KEV; the CVSS 4.3 Medium rating reflects the authentication prerequisite and the narrow confidentiality impact (existence inference only, no content disclosure).
Server-Side Request Forgery in Weblate's VCS_RESTRICT_PRIVATE control (versions 5.15 through pre-2026.6) allows bypassing of outbound request restrictions via IPv6 transition address encoding techniques. By supplying a hostname whose DNS AAAA record resolves to a NAT64-wrapped, 6to4-wrapped, or IPv4-compatible IPv6 address that encodes a private IPv4 endpoint, an attacker causes Weblate's validator to pass the address as globally routable while the host kernel routes the packet to the embedded private IPv4 target. The vulnerability carries High confidentiality impact (CVSS 5.9, AV:N/AC:H) because SSRF can expose internal services such as cloud IMDS credential endpoints; no public exploit or CISA KEV listing has been identified at time of analysis.
Low-severity path traversal in Weblate prior to 5.17 allows authenticated users to bypass repository boundary checks by crafting symlinks with colliding path prefixes, potentially reading files outside the intended repository scope. No active exploitation or public exploit code is known, and the vulnerability has been patched in version 5.17.
Server-side request forgery in Weblate's webhook add-on allows high-privileged users to bypass existing SSRF protections and make requests to internal network resources. Versions prior to 5.17 are affected; the fix introduces a new restriction setting that blocks private IP ranges by default. No active exploitation is reported (EPSS 0.01%, no CISA KEV entry), and no public exploit code has been identified at this time.
Server-Side Request Forgery in Weblate's project-level machine translation configuration allows an authenticated project administrator to probe internal network services and read partial responses. Any user holding the per-project 'Administration' role (which grants project.edit permission) can supply a crafted URL as a machine translation service endpoint; during validation Weblate issues an outbound HTTP request to that URL and reflects up to 200 characters of the response body in the resulting error message. All Weblate deployments running versions prior to 5.17 are affected; no public exploit code exists and no active exploitation has been confirmed at time of analysis.
Server-Side Request Forgery in Weblate prior to version 5.17 allows authenticated users to bypass the ALLOWED_ASSET_DOMAINS allowlist via HTTP redirects, forcing the server to request unintended hosts. This can lead to low confidentiality impact through information disclosure. The vulnerability is fixed in version 5.17, and no public exploit or active exploitation has been identified.
Path traversal in Weblate allows authenticated users to read arbitrary files outside the repository via the translation memory API. Versions prior to 5.17 are affected; the fix in 5.17 adds filename validation to prevent directory traversal and restricts remote URLs to allowed domains. No active exploitation has been reported (CISA KEV not listed, SSVC exploitation status none), and EPSS risk is very low (0.04%).
Low-privileged users can modify Weblate translation memory via improperly exposed API endpoints in versions prior to 5.17, leading to unauthorized data manipulation without affecting confidentiality or availability. The vulnerability is not known to be actively exploited and has a very low exploitation probability (EPSS 0.01%).
Weblate's tasks API prior to version 5.17 permitted authenticated users to retrieve operation logs for pending (in-flight) background tasks belonging to project scopes outside their access level. The access control check enforcing component-level permissions was not applied to tasks in PENDING state because the component context was unavailable until task completion; the fix caches component metadata at task creation so permissions can be verified regardless of task state. No public exploit code exists, exploitation probability is very low (EPSS 0.03%), and CISA KEV does not list this vulnerability.
Weblate versions prior to 5.16.1 fail to properly restrict API access to addon data, allowing authenticated users to enumerate and access all addons across every project and component in the system. An attacker with valid credentials can query the REST API endpoints to retrieve sensitive addon information that should be scoped to their assigned permissions. This information disclosure vulnerability is fixed in version 5.16.1.
Weblate versions up to 5.16.0 contains a vulnerability that allows attackers to an argument injection to `ssh-add` (CVSS 6.6).
Wlc versions prior to 1.17.0 fail to restrict unscoped API keys, allowing them to be transmitted to unintended Weblate servers and potentially leaked to attackers with local access or through compromised credentials. A local attacker with user privileges could exploit this information disclosure to gain unauthorized access to Weblate instances across multiple servers. A patch is available in version 1.17.0 and later.
wlc is a Weblate command-line client using Weblate's REST API. Prior to 1.17.0, the SSL verification would be skipped for some crafted URLs. [CVSS 2.5 LOW]
Improper input validation in Weblate versions prior to 5.15.1 lets a user who can submit translation files or restore project backups supply a crafted filename such as .git/config or a nested path/.git/config, overwriting the Git configuration inside a project working copy and overriding Git's behavior; the upstream advisory describes the outcome as remote code execution through Git config overwrite. Our assessment is that exploitation requires an authenticated account holding translation-upload or backup-restore privileges (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), even though the vendor's rating uses PR:N, and that full code execution additionally depends on Git honoring the injected directives during a later Git operation. Vendor-released patch: 5.15.1; no public exploit code and no confirmed active exploitation were identified at time of analysis.
Authenticated users of Weblate instances running versions prior to 5.15 can enumerate all user accounts and read other users' notification subscription settings through the REST API, because authorization checks on the user-list and user-notifications endpoints were incomplete. The flaw requires only a low-privileged or self-registered account (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, base 4.3) and leaks limited read-only information - usernames, account listing, and notification preferences - so impact is confidentiality-only and low. A vendor fix is available in Weblate 5.15, EPSS places exploitation likelihood at roughly 0.27% (18th percentile), and no public exploit code or confirmed active exploitation has been identified at time of analysis.
Information disclosure and mass repository update triggering in Weblate before 5.15 allow unauthenticated remote attackers to send crafted webhook payloads that exploit over-permissive repository full_name endswith matching, causing updates across many repositories and potentially revealing component existence. The vulnerability only applies where webhooks are enabled and the service hook endpoints are reachable; CVSS 3.1 scores it 5.3 with low confidentiality impact. No public exploit code or active exploitation was identified, EPSS is 0.26%, and the vendor fixed the issue in Weblate 5.15 while offering disabling ENABLE_HOOKS as a workaround.
Improper validation of invitation ownership in Weblate before 5.15 allows a different user to accept an invitation that was opened in another user's authenticated session, potentially obtaining the project access or membership that the invitation was intended to confer on someone else. Exploitation is not a network-reachable default condition: it requires low-privileged authenticated access to the victim's exposed session (CVSS 4.0 vector AV:L/AC:H/AT:P/PR:L/UI:P, base score 1.0; independent assessment CVSS 3.1 AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N), plus the precondition that the victim leaves an opened invitation unattended. There is no indication of active exploitation (not listed in CISA KEV), no public exploit code was identified at time of analysis, and EPSS is low at 0.35% (26th percentile); the vendor-released patch is Weblate 5.15.
Weblate is a web based localization tool. Rated low severity (CVSS 2.6), this vulnerability is remotely exploitable.
An open redirect in Weblate 5.13.2 and earlier lets a crafted link on the legitimate Weblate domain bounce a victim to an attacker-controlled site, and can be chained to trigger drive-by downloads. Exploitation is not unconditional: it requires a non-default deployment where Weblate is fronted by Anubis and the REDIRECT_DOMAINS setting has been left unset, and it demands victim interaction since the target must actively click the crafted URL (CVSS:3.1/AV:N/AC:H/PR:N/UI:R). The issue is fixed in 5.13.3, publicly available exploit details exist via the GitHub advisory, EPSS is low at 0.04% (12th percentile), and there is no indicator of confirmed active exploitation.
Weblate is a web based localization tool. Rated low severity (CVSS 2.1), this vulnerability is remotely exploitable.
A security vulnerability in Weblate (CVSS 5.3). Remediation should follow standard vulnerability management procedures. Vendor patch is available.
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.
Weblate is a web based localization tool. Rated low severity (CVSS 2.2), this vulnerability is remotely exploitable. Public exploit code available and no vendor patch available.
Weblate is a web based localization tool. Rated medium severity (CVSS 5.4), this vulnerability is remotely exploitable, low attack complexity.
The package weblate from 0 and before 4.11.1 are vulnerable to Remote Code Execution (RCE) via argument injection when using git or mercurial repositories. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity.
Weblate is a copyleft software web-based continuous localization system. Rated medium severity (CVSS 5.4), this vulnerability is remotely exploitable, low attack complexity. This Cross-Site Scripting (XSS) vulnerability could allow attackers to inject malicious scripts into web pages viewed by other users.
The password reset form in Weblate before 2.10.1 provides different error messages depending on whether the email address is associated with an account, which allows remote attackers to enumerate. Rated medium severity (CVSS 5.3), this vulnerability is remotely exploitable, no authentication required, low attack complexity. This Exposure of Sensitive Information vulnerability could allow attackers to access sensitive data that should not be disclosed.
Argument injection in Weblate's Mercurial backend lets an authenticated user with project-scoped component.edit permission plant a dash-prefixed repository filename that Mercurial later interprets as a command-line option instead of a literal path, resulting in arbitrary command execution with the privileges of the Weblate service account when the repository is next updated. The issue affects Weblate 4.11.1 through 2026.7.1 and is a residual, incomplete fix for CVE-2022-23915; although it carries a CVSS of 8.5, exploitation requires a Mercurial-backed RESX component using the 'Update RESX files' add-on plus a subsequent repository update, so the realistic attack surface is narrow. A vendor patch is available in Weblate 2026.8, and no public exploit identified at time of analysis.
Arbitrary file read via symlink traversal in Weblate's App store metadata ZIP download affects all versions prior to 2026.7, allowing project administrators to exfiltrate host files outside their repository boundary. The vulnerability is an incomplete fix for CVE-2026-34242 - the original patch blocked path traversal via '..' sequences but failed to prevent symlink-based traversal, leaving the arbitrary file read primitive intact. No public exploit has been identified at time of analysis; the CVSS score of 7.7 High reflects scope change due to cross-boundary file disclosure, while the project-administrator privilege requirement limits the exploitable population.
Weblate's REST API failed to enforce permission scope on team (group) assignments in all versions prior to 2026.7, allowing any authenticated low-privilege user to assign unauthorized projects or workspaces to a team via the API. The root serializer field `defining_workspace` resolved primary keys against `Workspace.objects.all()` without filtering by the requesting user's permissions, enabling horizontal privilege escalation to private projects. Vendor-released patch 2026.7 is confirmed; no public exploit code or CISA KEV listing exists at time of analysis.
Privilege escalation in Weblate versions prior to 5.17 allows an authenticated low-privileged user to modify sensitive fields (like roles or permissions) of any user account through the REST API's user patching endpoint, leading to full system compromise. The vulnerability stems from insufficient field-level authorization, and the EPSS exploitation probability is very low (0.04%) with no known active exploitation; a vendor patch is available in version 5.17.
Arbitrary file read vulnerability in Weblate versions prior to 5.17 allows authenticated attackers to read sensitive files from the server via symlink traversal in the ZIP download feature. No active exploitation or public exploit code has been identified, and the EPSS score (0.01%) indicates very low likelihood of exploitation. A vendor-released patch is available in Weblate 5.17.
Remote code execution in Weblate's project backup restoration affects versions prior to 5.17, exploitable by authenticated users with project-creation privileges. Backup archives were extracted without filtering Git (`.git/config`, `.git/hooks/*`, `.git/modules/`) and Mercurial (`.hg/hgrc`) configuration files, allowing a crafted archive to plant malicious VCS hooks or rewrite repository configuration. When Weblate subsequently performs git operations on the restored component, attacker-supplied hook scripts execute with server-process privileges. No public exploit or active exploitation has been confirmed (SSVC: Exploitation none; EPSS 0.33%).
The wlc Weblate command-line client prior to version 1.17.2 is vulnerable to arbitrary file write attacks through path traversal when downloading multi-translations from a malicious or compromised server. An authenticated attacker can exploit this vulnerability by crafting a specially designed server response to write files to arbitrary locations on the victim's system, potentially compromising system integrity. This vulnerability affects wlc versions before 1.17.2 and is fixed in the patched version.
Weblate versions prior to 5.15.2 expose screenshot images through the web server without authentication controls, enabling unauthenticated attackers to retrieve sensitive screenshots by predicting their filenames. This improper access control flaw affects all users whose screenshot content should be restricted. A patch is available in version 5.15.2 and later.
DNS rebinding SSRF in Weblate prior to version 2026.8 allows an authenticated user with VCS component URL management privileges to circumvent VCS_RESTRICT_PRIVATE protections and reach internal network services. The attack exploits the time gap between Weblate's initial hostname validation and the VCS client's subsequent independent DNS lookup - an attacker-controlled domain passes validation pointing to a public IP, then switches to an internal address before the actual VCS connection is made. Triggering a clone, fetch, push, or similar operation then causes Weblate to connect to internal VCS-compatible services and potentially expose their contents. No public exploit has been identified at time of analysis, though the DNS rebinding technique is well-understood and toolkits for it exist.
Object-scoped RSS feeds in Weblate prior to version 2026.8 bypass the platform's permission model, exposing change-history metadata from private projects and restricted components to any requester - including unauthenticated users on installations that permit anonymous access. The exposed metadata includes project and component identities, contributor usernames and full names, action types, timestamps, and translation unit links, enabling enumeration of contributor identity and project structure in otherwise-private deployments. No public exploit has been identified at time of analysis and this vulnerability is not listed in CISA KEV, but the lack of any exploitation prerequisite on anonymously accessible instances makes it straightforward to abuse with standard HTTP tooling.
Unbounded regular expression evaluation in Weblate prior to 2026.7 allows any authenticated user holding the built-in 'Edit source' role to induce sustained CPU exhaustion by storing a catastrophically-backtracking pattern in a source string's quality-check flags. Both the RegexCheck and PlaceholderCheck mechanisms compile user-supplied expressions at validation time but execute them without any runtime timeout, so a single malicious flag edit can pin server CPU indefinitely by re-triggering evaluation across every linked translation unit in the same request. No public exploit code exists and the issue is not listed in CISA KEV, but the low complexity and clear role-based attack path make it a credible internal or supply-chain threat for multi-contributor Weblate deployments.
Nested API change endpoints in Weblate prior to version 2026.7 bypass component-level access controls, exposing change history of restricted components to authenticated project members who lack direct view permissions. A low-privileged project member can call the project-, component-, or translation-level change list endpoints to enumerate change records for restricted components - including source and translated string content, component identity, and change metadata - that return 404 on direct component access. No public exploit or CISA KEV listing has been identified; real-world risk is conditional on use of Weblate's restricted component feature.
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.
Object existence enumeration in Weblate prior to version 2026.7 allows authenticated low-privilege users to infer whether objects exist within private projects by observing differential HTTP response codes - HTTP 403 (Forbidden) for existing-but-inaccessible objects versus HTTP 404 (Not Found) for truly absent ones. Affected endpoints performing globally-scoped ORM lookups across changes, comments, and announcements fail to restrict results to projects the requesting user is authorized to view. No public exploit has been identified and this is not listed in CISA KEV; the CVSS 4.3 Medium rating reflects the authentication prerequisite and the narrow confidentiality impact (existence inference only, no content disclosure).
Server-Side Request Forgery in Weblate's VCS_RESTRICT_PRIVATE control (versions 5.15 through pre-2026.6) allows bypassing of outbound request restrictions via IPv6 transition address encoding techniques. By supplying a hostname whose DNS AAAA record resolves to a NAT64-wrapped, 6to4-wrapped, or IPv4-compatible IPv6 address that encodes a private IPv4 endpoint, an attacker causes Weblate's validator to pass the address as globally routable while the host kernel routes the packet to the embedded private IPv4 target. The vulnerability carries High confidentiality impact (CVSS 5.9, AV:N/AC:H) because SSRF can expose internal services such as cloud IMDS credential endpoints; no public exploit or CISA KEV listing has been identified at time of analysis.
Low-severity path traversal in Weblate prior to 5.17 allows authenticated users to bypass repository boundary checks by crafting symlinks with colliding path prefixes, potentially reading files outside the intended repository scope. No active exploitation or public exploit code is known, and the vulnerability has been patched in version 5.17.
Server-side request forgery in Weblate's webhook add-on allows high-privileged users to bypass existing SSRF protections and make requests to internal network resources. Versions prior to 5.17 are affected; the fix introduces a new restriction setting that blocks private IP ranges by default. No active exploitation is reported (EPSS 0.01%, no CISA KEV entry), and no public exploit code has been identified at this time.
Server-Side Request Forgery in Weblate's project-level machine translation configuration allows an authenticated project administrator to probe internal network services and read partial responses. Any user holding the per-project 'Administration' role (which grants project.edit permission) can supply a crafted URL as a machine translation service endpoint; during validation Weblate issues an outbound HTTP request to that URL and reflects up to 200 characters of the response body in the resulting error message. All Weblate deployments running versions prior to 5.17 are affected; no public exploit code exists and no active exploitation has been confirmed at time of analysis.
Server-Side Request Forgery in Weblate prior to version 5.17 allows authenticated users to bypass the ALLOWED_ASSET_DOMAINS allowlist via HTTP redirects, forcing the server to request unintended hosts. This can lead to low confidentiality impact through information disclosure. The vulnerability is fixed in version 5.17, and no public exploit or active exploitation has been identified.
Path traversal in Weblate allows authenticated users to read arbitrary files outside the repository via the translation memory API. Versions prior to 5.17 are affected; the fix in 5.17 adds filename validation to prevent directory traversal and restricts remote URLs to allowed domains. No active exploitation has been reported (CISA KEV not listed, SSVC exploitation status none), and EPSS risk is very low (0.04%).
Low-privileged users can modify Weblate translation memory via improperly exposed API endpoints in versions prior to 5.17, leading to unauthorized data manipulation without affecting confidentiality or availability. The vulnerability is not known to be actively exploited and has a very low exploitation probability (EPSS 0.01%).
Weblate's tasks API prior to version 5.17 permitted authenticated users to retrieve operation logs for pending (in-flight) background tasks belonging to project scopes outside their access level. The access control check enforcing component-level permissions was not applied to tasks in PENDING state because the component context was unavailable until task completion; the fix caches component metadata at task creation so permissions can be verified regardless of task state. No public exploit code exists, exploitation probability is very low (EPSS 0.03%), and CISA KEV does not list this vulnerability.
Weblate versions prior to 5.16.1 fail to properly restrict API access to addon data, allowing authenticated users to enumerate and access all addons across every project and component in the system. An attacker with valid credentials can query the REST API endpoints to retrieve sensitive addon information that should be scoped to their assigned permissions. This information disclosure vulnerability is fixed in version 5.16.1.
Weblate versions up to 5.16.0 contains a vulnerability that allows attackers to an argument injection to `ssh-add` (CVSS 6.6).
Wlc versions prior to 1.17.0 fail to restrict unscoped API keys, allowing them to be transmitted to unintended Weblate servers and potentially leaked to attackers with local access or through compromised credentials. A local attacker with user privileges could exploit this information disclosure to gain unauthorized access to Weblate instances across multiple servers. A patch is available in version 1.17.0 and later.
wlc is a Weblate command-line client using Weblate's REST API. Prior to 1.17.0, the SSL verification would be skipped for some crafted URLs. [CVSS 2.5 LOW]
Improper input validation in Weblate versions prior to 5.15.1 lets a user who can submit translation files or restore project backups supply a crafted filename such as .git/config or a nested path/.git/config, overwriting the Git configuration inside a project working copy and overriding Git's behavior; the upstream advisory describes the outcome as remote code execution through Git config overwrite. Our assessment is that exploitation requires an authenticated account holding translation-upload or backup-restore privileges (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), even though the vendor's rating uses PR:N, and that full code execution additionally depends on Git honoring the injected directives during a later Git operation. Vendor-released patch: 5.15.1; no public exploit code and no confirmed active exploitation were identified at time of analysis.
Authenticated users of Weblate instances running versions prior to 5.15 can enumerate all user accounts and read other users' notification subscription settings through the REST API, because authorization checks on the user-list and user-notifications endpoints were incomplete. The flaw requires only a low-privileged or self-registered account (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, base 4.3) and leaks limited read-only information - usernames, account listing, and notification preferences - so impact is confidentiality-only and low. A vendor fix is available in Weblate 5.15, EPSS places exploitation likelihood at roughly 0.27% (18th percentile), and no public exploit code or confirmed active exploitation has been identified at time of analysis.
Information disclosure and mass repository update triggering in Weblate before 5.15 allow unauthenticated remote attackers to send crafted webhook payloads that exploit over-permissive repository full_name endswith matching, causing updates across many repositories and potentially revealing component existence. The vulnerability only applies where webhooks are enabled and the service hook endpoints are reachable; CVSS 3.1 scores it 5.3 with low confidentiality impact. No public exploit code or active exploitation was identified, EPSS is 0.26%, and the vendor fixed the issue in Weblate 5.15 while offering disabling ENABLE_HOOKS as a workaround.
Improper validation of invitation ownership in Weblate before 5.15 allows a different user to accept an invitation that was opened in another user's authenticated session, potentially obtaining the project access or membership that the invitation was intended to confer on someone else. Exploitation is not a network-reachable default condition: it requires low-privileged authenticated access to the victim's exposed session (CVSS 4.0 vector AV:L/AC:H/AT:P/PR:L/UI:P, base score 1.0; independent assessment CVSS 3.1 AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N), plus the precondition that the victim leaves an opened invitation unattended. There is no indication of active exploitation (not listed in CISA KEV), no public exploit code was identified at time of analysis, and EPSS is low at 0.35% (26th percentile); the vendor-released patch is Weblate 5.15.
Weblate is a web based localization tool. Rated low severity (CVSS 2.6), this vulnerability is remotely exploitable.
An open redirect in Weblate 5.13.2 and earlier lets a crafted link on the legitimate Weblate domain bounce a victim to an attacker-controlled site, and can be chained to trigger drive-by downloads. Exploitation is not unconditional: it requires a non-default deployment where Weblate is fronted by Anubis and the REDIRECT_DOMAINS setting has been left unset, and it demands victim interaction since the target must actively click the crafted URL (CVSS:3.1/AV:N/AC:H/PR:N/UI:R). The issue is fixed in 5.13.3, publicly available exploit details exist via the GitHub advisory, EPSS is low at 0.04% (12th percentile), and there is no indicator of confirmed active exploitation.
Weblate is a web based localization tool. Rated low severity (CVSS 2.1), this vulnerability is remotely exploitable.
A security vulnerability in Weblate (CVSS 5.3). Remediation should follow standard vulnerability management procedures. Vendor patch is available.
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.
Weblate is a web based localization tool. Rated low severity (CVSS 2.2), this vulnerability is remotely exploitable. Public exploit code available and no vendor patch available.
Weblate is a web based localization tool. Rated medium severity (CVSS 5.4), this vulnerability is remotely exploitable, low attack complexity.
The package weblate from 0 and before 4.11.1 are vulnerable to Remote Code Execution (RCE) via argument injection when using git or mercurial repositories. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity.
Weblate is a copyleft software web-based continuous localization system. Rated medium severity (CVSS 5.4), this vulnerability is remotely exploitable, low attack complexity. This Cross-Site Scripting (XSS) vulnerability could allow attackers to inject malicious scripts into web pages viewed by other users.
The password reset form in Weblate before 2.10.1 provides different error messages depending on whether the email address is associated with an account, which allows remote attackers to enumerate. Rated medium severity (CVSS 5.3), this vulnerability is remotely exploitable, no authentication required, low attack complexity. This Exposure of Sensitive Information vulnerability could allow attackers to access sensitive data that should not be disclosed.