Summary
XWiki configuration files can be accessed through jsx and sx endpoints
Workarounds
There is no known workaround, other than upgrading XWiki.
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 Gregor Neumann.
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.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
This has been patched in 17.4.0-rc-1, 16.10.7.
Frequently Asked Questions
- What is CVE-2025-55748? CVE-2025-55748 is a critical-severity security vulnerability in org.xwiki.platform:xwiki-platform-skin-skinx (maven), affecting versions >= 4.2-milestone-2, < 16.10.7. It is fixed in 16.10.7.
- Which versions of org.xwiki.platform:xwiki-platform-skin-skinx are affected by CVE-2025-55748? org.xwiki.platform:xwiki-platform-skin-skinx (maven) versions >= 4.2-milestone-2, < 16.10.7 is affected.
- Is there a fix for CVE-2025-55748? Yes. CVE-2025-55748 is fixed in 16.10.7. Upgrade to this version or later.
- Is CVE-2025-55748 exploitable, and should I be worried? Whether CVE-2025-55748 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-55748 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-55748? Upgrade
org.xwiki.platform:xwiki-platform-skin-skinxto 16.10.7 or later.