GHSA-xq3r-2qv5-vqqm
Fix: xwiki/xwiki-commons@a979cafGHSA-xq3r-2qv5-vqqm is a CWE-23 vulnerability in org.xwiki.commons:xwiki-commons-classloader-api. EPSS puts its 30-day exploitation probability at 19.6% (97th percentile). O3 Security confirms whether GHSA-xq3r-2qv5-vqqm is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
XWiki Platform has path traversal via resources parameter in ssx and jsx endpoints when using leading slash
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-xq3r-2qv5-vqqm.
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.
Real-World Exposure
org.xwiki.commons:xwiki-commons-classloader-api☕org.xwiki.commons:xwiki-commons-classloader-api☕org.xwiki.commons:xwiki-commons-classloader-api☕org.xwiki.commons:xwiki-commons-classloader-apiReal-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
It's possible to get access and read configuration files by using URLs such as http://localhost:8080/bin/ssx/Main/WebHome?resource=/../../WEB-INF/xwiki.cfg&minify=false.
This can apparently be reproduced on Tomcat instances.
Patches
This has been patched in 18.0.0-rc-1, 17.10.3, 17.4.9, 16.10.17.
Workarounds
There is no known workaround, other than upgrading XWiki.
References
- https://jira.xwiki.org/browse/XCOMMONS-3547
- https://github.com/xwiki/xwiki-commons/commit/a979cafd89f6a9c9c0b9ab19744d672df64429bf
For more information
If you have any questions or comments about this advisory:
- Open an issue in Jira XWiki.org
- Email us at Security Mailing List
Attribution
The vulnerability was reported by Michał Kołek.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.xwiki.commons:xwiki-commons-classloader-api | ≥ 4.2-milestone-2&&< 16.10.17 | 16.10.17 |
| ☕Maven | org.xwiki.commons:xwiki-commons-classloader-api | ≥ 17.0.0-rc-1&&< 17.4.9 | 17.4.9 |
| ☕Maven | org.xwiki.commons:xwiki-commons-classloader-api | ≥ 17.5.0&&< 17.10.3 | 17.10.3 |
| ☕Maven | org.xwiki.commons:xwiki-commons-classloader-api | ≥ 18.0.0-rc-1&&< 18.1.0-rc-1 | 18.1.0-rc-1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.commons:xwiki-commons-classloader-api. 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.
Fix
Update org.xwiki.commons:xwiki-commons-classloader-api to 16.10.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xq3r-2qv5-vqqm 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 pinpoints whether GHSA-xq3r-2qv5-vqqm 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-xq3r-2qv5-vqqm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-xq3r-2qv5-vqqm in your dependencies?
O3 detects GHSA-xq3r-2qv5-vqqm across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.