Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:HSummary
CVE-2023-31126 is a critical-severity Improper Neutralization of Invalid Characters in Identifiers in Web Pages (CWE-86) vulnerability in Xwiki Xwiki. Its CVSS base score is 9.0 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Browser Session Hijacking (T1185); ranked in the top 46% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
The vulnerability is a cross-site scripting flaw in the HTML sanitizer component of org.xwiki.commons:xwiki-commons-xml, the XML library used by the XWiki open-source wiki platform. Introduced with version 14.6-rc-1, the sanitizer permits arbitrary HTML injection through invalid data attributes; the issue does not affect restricted cleaning modes in HTMLCleaner, where characters such as / and > are stripped from attribute names.
An attacker with low privileges can supply crafted input containing malicious data attributes to achieve reflected or stored XSS, resulting in high impact on confidentiality, integrity, and availability as reflected in the CVSS 9.0 score.
Advisories and patches from the XWiki project state that the problem is resolved in versions 14.10.4 and 15.0 RC1 by restricting data attribute names to allowed characters; the corresponding fixes are documented in the referenced GitHub commits and XCOMMONS-2606 Jira ticket, with no workarounds other than upgrading.
The EPSS score remains flat at its peak value of 0.2162 with no material upward trajectory after disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-1603
Vulnerability Data
`org.xwiki.commons:xwiki-commons-xml` is an XML library used by the open-source wiki platform XWiki. The HTML sanitizer, introduced in version 14.6-rc-1, allows the injection of arbitrary HTML code and thus cross-site scripting via invalid data attributes. This vulnerability does not affect restricted…
more
cleaning in HTMLCleaner as there attributes are cleaned and thus characters like `/` and `>` are removed in all attribute names. This problem has been patched in XWiki 14.10.4 and 15.0 RC1 by making sure that data attributes only contain allowed characters. There are no known workarounds apart from upgrading to a version including the fix.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.1.2V1.3.2
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.
Penetration testing submits XSS payloads to web applications, detecting cross-site scripting flaws for subsequent remediation.
Validates web inputs to reject script-related content that could produce XSS.
Output validation against expected content can reject or sanitize script content in generated web pages, reducing XSS exploitability.
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.
Secure SDLC practices directly require proper input neutralization and validation to prevent identifier-handling flaws.
Patching and EOL replacement can remediate known XSS instances in libraries or frameworks (partial) but do nothing to enforce input neutralization in application code (none).
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.
Security testing can detect the weakness but does not itself implement the neutralization controls.
Knowledge exchange on emerging attack techniques and patches reduces the likelihood that cross-site scripting flaws remain unaddressed in deployed applications.
Operational indicators of compromise for web-application attacks can be incorporated into WAF or input-filtering rules, lowering the likelihood that unsanitized data reaches the browser.
Secure development life cycle mandates input validation and sanitization that directly prevents improper neutralization of invalid characters in identifiers.
Application security requirements explicitly call for validation of all inputs including identifiers, mitigating this weakness.
Secure coding standards require proper neutralization of invalid characters in tag names, URIs and identifiers, directly addressing CWE-86.