How severe is GHSA-h2g5-2rhx-ffgj?

No CVSS score has been assigned to GHSA-h2g5-2rhx-ffgj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-h2g5-2rhx-ffgj?

GHSA-h2g5-2rhx-ffgj affects the following packages: weblate (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-h2g5-2rhx-ffgj?

Update weblate to 4.11.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h2g5-2rhx-ffgj is resolved across your whole dependency graph.

How do I detect GHSA-h2g5-2rhx-ffgj in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for weblate. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-h2g5-2rhx-ffgj if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-h2g5-2rhx-ffgj?

O3 pinpoints whether GHSA-h2g5-2rhx-ffgj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-h2g5-2rhx-ffgj actively exploited in the wild?

No public exploit code has been indexed for GHSA-h2g5-2rhx-ffgj yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-h2g5-2rhx-ffgj?

GHSA-h2g5-2rhx-ffgj is classified as CWE-88 (CWE-88). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-h2g5-2rhx-ffgj published, and has it been updated?

GHSA-h2g5-2rhx-ffgj was published on March 5, 2022 and was last updated on February 3, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Withdrawn — this advisory has been retracted

🐍 PyPI

Not in CISA KEV

GHSA-h2g5-2rhx-ffgj

Fix: WeblateOrg/weblate@35d59f1

GHSA-h2g5-2rhx-ffgj is a CWE-88 vulnerability in weblate. O3 Security confirms whether GHSA-h2g5-2rhx-ffgj is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Duplicate Advisory: Command injection in Weblate

Also known asBIT-weblate-2022-23915CVE-2022-23915 CVE-2022-24727 GHSA-3872-f48p-pxqjPYSEC-2022-162PYSEC-2022-31

Published

Mar 5, 2022

Updated

Feb 3, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Feb 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍weblate

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-3872-f48p-pxqj. This link is maintained to preserve external references.

Original Description

Weblate is a web based localization tool with tight version control integration. Prior to version 4.11.1, Weblate didn't properly sanitize some arguments passed to Git and Mercurial, allowing them to change their behavior in an unintended way. Instances where untrusted users cannot create new components are not affected. The issues were fixed in the 4.11.1 release.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`weblate`	all versions	4.11.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for weblate. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update weblate to 4.11.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h2g5-2rhx-ffgj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-h2g5-2rhx-ffgj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-h2g5-2rhx-ffgj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Duplicate Advisory This advisory has been withdrawn because it is a duplicate of GHSA-3872-f48p-pxqj. This link is maintained to preserve external references. ## Original Description Weblate is a web based localization tool with tight version control integration. Prior to version 4.11.1, Weblate didn't properly sanitize some arguments passed to Git and Mercurial, allowing them to change their behavior in an unintended way. Instances where untrusted users cannot create new components are not affected. The issues were fixed in the 4.11.1 release.

O3 Security · Impact-Aware SCA

Is GHSA-h2g5-2rhx-ffgj in your dependencies?

O3 detects GHSA-h2g5-2rhx-ffgj across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works