Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍 PyPI

GHSA-6jp6-9rf9-gc66

MEDIUM

Cross-site Scripting in Weblate

Also known asBIT-weblate-2022-24710CVE-2022-24710PYSEC-2022-35
Published
Feb 25, 2022
Updated
Nov 19, 2024
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.7%probability of exploitation in next 30 days
Lower Risk49th percentile+0.41%
0.00%0.41%0.82%1.22%0.3%0.7%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

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:

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIweblateall versions4.11

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. Fix

    Update weblate to 4.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6jp6-9rf9-gc66 is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-6jp6-9rf9-gc66 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-6jp6-9rf9-gc66. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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
O3 Security · Impact-Aware SCA

Is GHSA-6jp6-9rf9-gc66 in your dependencies?

O3 detects GHSA-6jp6-9rf9-gc66 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.