CVE-2023-26472
Xwiki 6.2.1 – 13.10.10
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-26472 is a critical-severity Improper Encoding or Escaping of Output (CWE-116) vulnerability in Xwiki Xwiki. Its CVSS base score is 9.9 (Critical).
Operationally, ranked in the top 35% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
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 contains an improper output encoding flaw that permits execution of arbitrary wiki content under the privileges of the IconThemeSheet author. The issue affects all versions beginning with 6.2-milestone-1 and is triggered when an attacker creates a specially crafted icon theme, either by editing a new page or by modifying the user profile even when the account lacks general edit rights.
An authenticated attacker with low privileges can therefore obtain full read, write, and administrative control over wiki content, achieving a CVSS 9.9 impact that crosses security boundaries. The attack requires no user interaction and can be performed remotely over the network.
The GitHub Security Advisory and XWiki Jira entry recommend immediate upgrade to versions 14.9, 14.4.6, or 13.10.10. As a workaround, administrators can apply the patch from commit 48caf7491595238af2b531026a614221d5d61f38 directly to the IconThemesCode.IconThemeSheet page.
EPSS remains flat at 0.1031 with no material increase after disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-1122
Vulnerability Data
XWiki Platform is a generic wiki platform. Starting in version 6.2-milestone-1, one can execute any wiki content with the right of IconThemeSheet author by creating an icon theme with certain content. This can be done by creating a new page…
more
or even through the user profile for users not having edit right. The issue has been patched in XWiki 14.9, 14.4.6, and 13.10.10. An available workaround is to fix the bug in the page `IconThemesCode.IconThemeSheet` by applying a modification from commit 48caf7491595238af2b531026a614221d5d61f38.
- CWE(s)
Related Threats
CVEs Like This One
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.
Validating that output matches expected content directly mitigates failures to properly encode or escape data for its destination context.
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.
A.8.25 mandates secure SDLC practices including secure coding guidelines, security requirements, checkpoints, testing (scans/penetration), and developer training that reach output encoding/escaping to stop injection-style exploits, but leaves a bounded remainder (e.g. ad-hoc/non-SDLC code changes, incomplete guideline enforcement, or non-software outputs)
Application security requirements include explicit rules for safe output handling and encoding.
A.8.27 mandates security-by-design principles (including distrust external input, secure session control, data validation/sanitization, defense-in-depth, and design reviews against attack patterns) that reach output encoding/escaping for many common channels, but leaves a bounded remainder (e.g. ad-hoc or non-reviewed custom protocols, unsafe string concatenation in obscure sinks, or cases where the principles are only documented and not enforced in implementation).
Secure coding standards explicitly require correct output encoding and escaping to preserve message structure.
Security testing can detect missing or incorrect encoding but does not itself implement the control.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-116, a class-level weakness, and none of its children carries one either.