How severe is CVE-2022-24710?

CVE-2022-24710 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-24710?

CVE-2022-24710 affects the following packages: weblate (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2022-24710?

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

How do I detect CVE-2022-24710 in my PyPI 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-24710 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

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

No public exploit code has been indexed for CVE-2022-24710 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 is the EPSS score for CVE-2022-24710?

CVE-2022-24710 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 54th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-24710?

CVE-2022-24710 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

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

CVE-2022-24710 was published on February 25, 2022 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

MEDIUM severity

CVE-2022-24710 — weblate

MEDIUMFix: WeblateOrg/weblate@22d577b

CVE-2022-24710 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in weblate. A fix is available for weblate — see the affected versions and patch details below.

Cross-site Scripting in Weblate

Also known asBIT-weblate-2022-24710GHSA-6jp6-9rf9-gc66PYSEC-2022-35

Published

Feb 25, 2022

Updated

Aug 12, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs54th percentile — riskier than 54% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2022-24710 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

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

Impact

Due to improper neutralization, it was possible to perform cross-site scripting via crafted user and language names.

Patches

The issues were fixed in the 4.11 release. The following commits are addressing it:

f6753a1a1c63fade6ad418fbda827c6750ab0bda
9e19a8414337692cc90da2a91c9af5420f2952f1
22d577b1f1e88665a88b4569380148030e0f8389

Workarounds

You can look for crafted user and language names to see if you were affected.

References

For more information

If you have any questions or comments about this advisory:

Open a topic in discussions
Email us at [email protected]

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`weblate`	all versions	4.11`pip install --upgrade 'weblate==4.11'`

Affected Products

1 product · 1 configurations

Application

weblateweblate

< 4.11

range

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 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24710 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### Impact Due to improper neutralization, it was possible to perform cross-site scripting via crafted user and language names. ### Patches The issues were fixed in the 4.11 release. The following commits are addressing it: * f6753a1a1c63fade6ad418fbda827c6750ab0bda * 9e19a8414337692cc90da2a91c9af5420f2952f1 * 22d577b1f1e88665a88b4569380148030e0f8389 ### Workarounds You can look for crafted user and language names to see if you were affected. ### References * https://hackerone.com/reports/1486674 * https://hackerone.com/reports/1486718 * https://hackerone.com/reports/1485226 ### For mor