CVE-2026-23734
XWiki Platform: Path traversal via resources parameter in ssx and jsx endpoints when using leading slash
Blast Radius
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
XWiki Platform is a generic wiki platform. Versions prior to 18.1.0-rc-1, 17.10.3, 17.4.9, and 16.10.17 allow access to read configuration files by using URLs such as http://localhost:8080/bin/ssx/Main/WebHome?resource=/../../WEB-INF/xwiki.cfg&minify=false, leading to Path Traversal. The vulnerability is can be exploited via resources parameter the ssx and jsx endpoints by using leading slashes. This issue has been patched in 18.1.0-rc-1, 17.10.3, 17.4.9, 16.10.17.
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 CVE-2026-23734 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 CVE-2026-23734 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 CVE-2026-23734. 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-2026-23734 in your dependencies?
O3 detects CVE-2026-23734 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.