How severe is CVE-2022-24727?

No CVSS score has been assigned to CVE-2022-24727 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2022-24727?

CVE-2022-24727 affects the following packages: weblate (Bitnami). Ecosystems affected: Bitnami.

How do I fix CVE-2022-24727?

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

How do I detect CVE-2022-24727 in my Bitnami dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for weblate, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-24727 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.

Is CVE-2022-24727 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-24727 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.

When was CVE-2022-24727 published, and has it been updated?

CVE-2022-24727 was published on March 6, 2024 and was last updated on March 6, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 Bitnami

Not in CISA KEV

CVE-2022-24727 — weblate

Fix: WeblateOrg/weblate#7337

CVE-2022-24727 is a remote code execution vulnerability in weblate. A fix is available for weblate — see the affected versions and patch details below.

Also known asCVE-2022-23915 GHSA-3872-f48p-pxqj GHSA-h2g5-2rhx-ffgjPYSEC-2022-162PYSEC-2022-31SNYK-PYTHON-WEBLATE-2414088

Published

Mar 6, 2024

Updated

Mar 6, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 6, 2024 · 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 Bitnami packages — download data is not available via public APIs for these ecosystems.

Description

Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2022-23915. Reason: This candidate is a reservation duplicate of CVE-2022-23915. Notes: All CVE users should reference CVE-2022-23915 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Bitnami	`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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update weblate to 4.11.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24727 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.

Frequently Asked Questions

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. Authenticated users, can change the behavior of the application in an unintended way, leading to command execution.

O3 Security · Impact-Aware SCA

Is CVE-2022-24727 in your dependencies?

Find it across Bitnami, including transitive dependencies.

Scan my dependencies How O3 SCA works