CVE-2025-55749
Published: 01 December 2025
Summary
CVE-2025-55749 is a high-severity Improper Access Control (CWE-284) vulnerability in Xwiki Xwiki. Its CVSS base score is 8.7 (High).
Operationally, ranked in the top 23.0% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
XWiki is an open-source wiki platform that, in versions 16.7.0 through the fixed releases 16.10.11, 17.4.4, and 17.7.0 when deployed via the XWiki Jetty package, exposes a context permitting static access to any file under the webapp/ directory. This exposure can reveal files that store credentials and is tracked under CWE-284 with a CVSS 4.0 score of 8.7 reflecting network-accessible confidentiality impact without authentication.
An unauthenticated remote attacker can directly request arbitrary files in the webapp/ folder of an affected XJetty instance, allowing retrieval of sensitive configuration or credential material that would otherwise remain protected.
The GitHub Security Advisory GHSA-53gx-j3p6-2rw9 and linked commits document the root cause and confirm the issue is resolved by the version upgrades listed above; the XWiki Jira entry XWIKI-23438 provides additional patch references.
EPSS rose from low values to a recorded peak of 0.0203 on 2026-02-07 before receding to the current 0.0097, indicating a temporary increase in exploitation interest after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-200075
Vulnerability details
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…
more
allows accessing files which might contains credentials. Fixed in 16.10.11, 17.4.4, and 17.7.0.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
The access control policy and procedures directly mandate and enforce proper access control mechanisms across the organization.
Device lock enforces restricted access until re-authentication, directly reducing unauthorized use of active sessions.
Supervision and review of access control activities directly detects and remediates improper access configurations or usages.
Explicitly identifying and documenting actions permitted without identification or authentication enforces proper access control boundaries by defining justified exceptions.
By automatically labeling outputs with security attributes, the control supports attribute-based enforcement and reduces exploitability of improper access control weaknesses.
Associating and retaining security attributes with data directly supports enforcement of access control decisions across storage, processing, and transmission.
Requiring prior authorization for each remote access type prevents improper access control over remote connections.
Requiring authorization of wireless access before allowing connections enforces proper access control for this access method.