CVE-2022-24821 — xwiki-platform-skin-skinx
MEDIUMCVE-2022-24821 is a medium-severity (CVSS 6.8) CWE-648 vulnerability in org.xwiki.platform:xwiki-platform-skin-skinx. 1 public exploit reference exists, so weaponization risk is real. A fix is available for org.xwiki.platform:xwiki-platform-skin-skinx — see the affected versions and patch details below.
Incorrect Use of Privileged APIs in org.xwiki.platform.skin.skinx
EPSS Exploitation Probability
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.
How urgent is this, really
CVE-2022-24821 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.xwiki.platform:xwiki-platform-skin-skinx☕org.xwiki.platform:xwiki-platform-skin-skinx☕org.xwiki.platform:xwiki-platform-skin-skinxReal-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:
- Open an issue in JIRA
- Email us at XWiki Security ML
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.xwiki.platform:xwiki-platform-skin-skinx | ≥ 13.5.0&&< 13.10 | 13.10org.xwiki.platform:xwiki-platform-skin-skinx:13.10 |
| ☕Maven | org.xwiki.platform:xwiki-platform-skin-skinx | all versions | 12.10.11org.xwiki.platform:xwiki-platform-skin-skinx:12.10.11 |
| ☕Maven | org.xwiki.platform:xwiki-platform-skin-skinx | ≥ 13.0.0&&< 13.4.6 | 13.4.6org.xwiki.platform:xwiki-platform-skin-skinx:13.4.6 |
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 dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-skin-skinx, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 CVE-2022-24821 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-24821 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2022-24821. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-24821 in your dependencies?
O3 Security finds CVE-2022-24821 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.