CVE-2025-55749

Workarounds

The workaround is to modify the start_xwiki.sh script following https://github.com/xwiki/xwiki-platform/compare/8b68d8a70b43f25391b3ee48477d7eb71b95cf4b...99a04a0e2143583f5154a43e02174155da7e8e10.

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

Vulnerability reported by Joseph Huber.

In an instance which is using the XWiki Jetty package (XJetty), a context is exposed to statically access any file located in the webapp/ folder.

It allows accessing files which might contains credentials, like http://myhots/webapps/xwiki/WEB-INF/xwiki.cfg, http://myhots/webapps/xwiki/WEB-INF/xwiki.properties or http://myhots/webapps/xwiki/WEB-INF/hibernate.cfg.xml.

CVE-2025-55749 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (16.10.11, 17.4.4, 17.7.0); upgrading removes the vulnerable code path.

Kodem intelligence

This has been patched in 16.10.11, 17.4.4, 17.7.0.

1. What is CVE-2025-55749? CVE-2025-55749 is a high-severity security vulnerability in org.xwiki.platform:xwiki-platform-tool-jetty-resources (maven), affecting versions >= 16.7.0, < 16.10.11. It is fixed in 16.10.11, 17.4.4, 17.7.0.
2. How severe is CVE-2025-55749? CVE-2025-55749 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.xwiki.platform:xwiki-platform-tool-jetty-resources are affected by CVE-2025-55749? org.xwiki.platform:xwiki-platform-tool-jetty-resources (maven) versions >= 16.7.0, < 16.10.11 is affected.
4. Is there a fix for CVE-2025-55749? Yes. CVE-2025-55749 is fixed in 16.10.11, 17.4.4, 17.7.0. Upgrade to this version or later.
5. Is CVE-2025-55749 exploitable, and should I be worried? Whether CVE-2025-55749 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
6. What actually determines whether CVE-2025-55749 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.
7. How do I fix CVE-2025-55749?
   • Upgrade org.xwiki.platform:xwiki-platform-tool-jetty-resources to 16.10.11 or later
   • Upgrade org.xwiki.platform:xwiki-platform-tool-jetty-resources to 17.4.4 or later
   • Upgrade org.xwiki.platform:xwiki-platform-tool-jetty-resources to 17.7.0 or later