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

GHSA-ghcq-472w-vf4h

MEDIUM

Incorrect Use of Privileged APIs in org.xwiki.platform.skin.skinx

Also known asCVE-2022-24821
Published
Apr 8, 2022
Updated
Nov 8, 2023
Affected
3 pkgs
Patched
3 / 3
Exploits
1 known

EPSS Exploitation Probability

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk51th percentile+0.07%
0.20%0.56%0.91%1.27%0.7%0.8%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

3 pkgs affected
org.xwiki.platform:xwiki-platform-skin-skinxorg.xwiki.platform:xwiki-platform-skin-skinxorg.xwiki.platform:xwiki-platform-skin-skinx

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

Description

Impact

Simple users can create global SSX/JSX without specific rights: in theory only users with Programming Rights should be allowed to create SSX or JSX that are executed everywhere on a wiki. But a bug allow anyone with edit rights to actually create those.

Patches

This issue has been patched in XWiki 13.10-rc-1, 12.10.11 and 13.4.6.

Workarounds

There's no easy workaround for this issue, administrators should upgrade their wiki.

References

https://jira.xwiki.org/browse/XWIKI-19155

For more information

If you have any questions or comments about this advisory:

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.xwiki.platform:xwiki-platform-skin-skinx13.5.0&&< 13.1013.10
Mavenorg.xwiki.platform:xwiki-platform-skin-skinxall versions12.10.11
Mavenorg.xwiki.platform:xwiki-platform-skin-skinx13.0.0&&< 13.4.613.4.6
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-skin-skinx. 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 org.xwiki.platform:xwiki-platform-skin-skinx to 13.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ghcq-472w-vf4h 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-ghcq-472w-vf4h 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-ghcq-472w-vf4h. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Simple users can create global SSX/JSX without specific rights: in theory only users with Programming Rights should be allowed to create SSX or JSX that are executed everywhere on a wiki. But a bug allow anyone with edit rights to actually create those. ### Patches This issue has been patched in XWiki 13.10-rc-1, 12.10.11 and 13.4.6. ### Workarounds There's no easy workaround for this issue, administrators should upgrade their wiki. ### References https://jira.xwiki.org/browse/XWIKI-19155 ### For more information If you have any questions or comments about this advisory: * Op
O3 Security · Impact-Aware SCA

Is GHSA-ghcq-472w-vf4h in your dependencies?

O3 detects GHSA-ghcq-472w-vf4h across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.