CVE-2025-55749: The XWiki Jetty package (XJetty) allows accessing any application file through URL
Impact
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.
Patches
This has been patched in 16.10.11, 17.4.4, 17.7.0.
Workarounds
The workaround is to modify the startxwiki.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.
Other sources
XWiki is an open-source wiki software platform. From 16.7.0 to 16.10.11, 17.4.4, or 17.7.0, 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. Fixed in 16.10.11, 17.4.4, and 17.7.0.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2025-55749?
CVE-2025-55749 is considered a critical vulnerability due to the potential exposure of sensitive files containing credentials.
How do I fix CVE-2025-55749?
To fix CVE-2025-55749, upgrade the XWiki Jetty package to version 17.7.0, 17.4.4, or 16.10.11 depending on your current version.
What is the impact of CVE-2025-55749?
The impact of CVE-2025-55749 is that it allows unauthorized access to files in the webapp/ directory, potentially exposing sensitive information.
Which versions of XWiki are affected by CVE-2025-55749?
Versions of XWiki Jetty package between 17.0.0-rc-1 to 17.7.0, 16.7.0 to 16.10.11, and 17.0.0 to 17.4.4 are affected by CVE-2025-55749.
Is CVE-2025-55749 actively being exploited?
There have been reports indicating that CVE-2025-55749 could be actively exploited in the wild, emphasizing the need for immediate remediation.