CVE-2025-29925
Xwiki 1.9 – 15.10.14
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2025-29925 is a high-severity Resource Leak (CWE-402) vulnerability in Xwiki Xwiki. Its CVSS base score is 8.7 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked in the top 43% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
XWiki Platform, a generic wiki platform, contains an information disclosure vulnerability in its REST API prior to versions 15.10.14, 16.4.6, and 16.10.0-rc-1. The endpoint /rest/wikis/[wikiName]/pages returns a list of pages without enforcing view rights checks, exposing protected content even when the wiki is configured with restrictions such as "Prevent unregistered user to view pages." The flaw is tracked under CWE-402 and carries a CVSS 4.0 score of 8.7 reflecting network-accessible confidentiality impact without authentication.
An unauthenticated attacker can issue a simple HTTP request to the affected REST endpoint and enumerate page titles and structures that should remain hidden. This allows discovery of sensitive or internal wiki content across the main wiki, providing a foothold for further targeted attacks without triggering standard access controls.
The official XWiki advisory and linked commits indicate that the patched releases continue to accept requests to the endpoint but now filter results according to the caller's page-level permissions. Administrators are advised to upgrade to one of the fixed versions; no other workarounds are documented in the references.
EPSS remains low at 0.0115 with no significant post-disclosure increase observed.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-6735
Vulnerability Data
XWiki Platform is a generic wiki platform. Prior to 15.10.14, 16.4.6, and 16.10.0-rc-1, protected pages are listed when requesting the REST endpoints /rest/wikis/[wikiName]/pages even if the user doesn't have view rights on them. It's particularly true if the entire wiki…
more
is protected with "Prevent unregistered user to view pages": the endpoint would still list the pages of the wiki, though only for the main wiki. The problem has been patched in XWiki 15.10.14, 16.4.6, 16.10.0RC1. In those versions the endpoint can still be requested but the result is filtered out based on pages rights.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 2 hardening rules · 2 OS baselines
V3.5.8
Mitigating Controls (NIST 800-53 r5) AI
Explicitly enforces information-flow rules that block private resources from reaching unauthorized external spheres.
Enforces approved authorizations so private resources cannot be transmitted outside their intended sphere.
Boundary controls monitor and restrict communications that would otherwise leak private resources.
Requires confidentiality protection on transmitted data, directly stopping exposure of private resources.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Enforcing least-privilege access permissions directly prevents private resources from being exposed outside their intended sphere.
Logical segmentation and unauthorized-access protections stop resources from leaking into untrusted domains.
Encryption of data-at-rest reduces the value of any leaked resource but does not address the transmission flaw itself.
Protecting data-in-transit mitigates exposure during movement yet does not prevent the underlying boundary violation.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Information-access-restriction directly prevents private resources from being exposed beyond intended boundaries.
Access-control mechanisms limit who can receive resources that should remain internal.
Managing access rights helps ensure resources are not granted to untrusted parties.
Data-leakage-prevention technologies specifically block unintended transmission of sensitive resources.
Information-transfer rules can prevent unintended disclosure of private resources outside the product.
Network-security controls can limit exposure paths but do not address the root resource-leak logic.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (1 rule)
- V-248579 OL 8 must restrict access to the kernel message buffer. prevents CWE-402
Oracle Linux 9 (1 rule)
- V-271745 OL 9 must restrict access to the kernel message buffer. prevents CWE-402