Overview
CVE-2025-55749 describes a file disclosure vulnerability affecting XWiki, a widely used open-source wiki platform. This vulnerability, present in specific versions when using the XJetty package, allows unauthorized access to files within the web application directory. This can potentially expose sensitive information, including credentials, leading to significant security risks.
Technical Details
The vulnerability stems from a publicly accessible context that allows static access to any file located within the webapp/ directory of the XWiki installation. This directory typically contains configuration files, scripts, and other sensitive data that should not be directly accessible to unauthorized users. The use of the XWiki Jetty package (XJetty) is a requirement for this vulnerability to be exploitable.
Specifically, the affected versions are those from 16.7.0 up to 16.10.11, 17.4.4, and 17.7.0.
CVSS Analysis
Due to the information provided by the reporter, the CVSS score is N/A and Severity is N/A. However, given the potential for exposing credentials and sensitive configuration data, the impact of a successful exploit could be significant. It is highly recommended to apply the available patches as soon as possible.
Possible Impact
Successful exploitation of CVE-2025-55749 could lead to the following consequences:
- Credential Theft: Exposure of database passwords, API keys, and other sensitive credentials stored in configuration files.
- Data Breach: Unauthorized access to sensitive data stored within the XWiki application.
- System Compromise: Exposure of critical application files that could allow an attacker to further compromise the XWiki instance or the underlying server.
Mitigation or Patch Steps
The vulnerability has been addressed in the following XWiki versions:
- 16.10.11
- 17.4.4
- 17.7.0
To mitigate the risk, it is strongly recommended to upgrade your XWiki installation to one of these versions or a later version. If immediate patching is not possible, consider implementing temporary workarounds such as restricting access to the webapp/ directory at the web server level, but be aware that this may impact functionality.
