CVE-2023-26055
Xwiki Commons 3.2 – 13.10.9
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-26055 is a critical-severity Improper Neutralization of Escape, Meta, or Control Sequences (CWE-150) vulnerability in Xwiki Commons. Its CVSS base score is 9.9 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked in the top 33% 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 Commons, the shared technical libraries used across multiple XWiki projects, contain an improper neutralization flaw (CWE-150) that permits stored code injection. The issue affects all versions starting from 3.1-milestone-1 and manifests when short text properties are rendered, including user profile pages and any application built with Apps Within Minutes that employs a short text field.
Any authenticated user with permission to edit their own profile or comparable short text fields can supply malicious code that executes with programming rights. Because the vulnerability is exploitable over the network with low attack complexity and no user interaction, an attacker can achieve full confidentiality, integrity, and availability impact within the affected XWiki instance, including scope change to other components.
Public advisories hosted on GitHub and the corresponding XWiki JIRA issues (XCOMMONS-2498, XWIKI-19793, XWIKI-19794) state that the flaw is resolved in releases 13.10.9, 14.4.4, and 14.7RC1; administrators are advised to upgrade to one of these versions.
EPSS scores have remained low, moving only from a peak of 0.0505 to a current value of 0.0490, indicating limited observed exploitation interest since disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-0944
Vulnerability Data
XWiki Commons are technical libraries common to several other top level XWiki projects. Starting in version 3.1-milestone-1, any user can edit their own profile and inject code, which is going to be executed with programming right. The same vulnerability can…
more
also be exploited in all other places where short text properties are displayed, e.g., in apps created using Apps Within Minutes that use a short text field. The problem has been patched on versions 13.10.9, 14.4.4, 14.7RC1.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.10V1.3.12
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 input neutralization and escaping to prevent this class of flaw.
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 escape/sequence neutralization; this prevents exploitation for many instances but leaves a bounded remainder where implementation is incomplete or the specific sequences are missed.
A.8.26 requires identifying and specifying requirements including resilience against SQL injections, input validation, and output controls (items d, j, l, m, n), which when addressed stop exploitation of unneutralized escape sequences; this covers only a minority slice of CWE-150's broader meta/control sequences and downstream contexts, with the bulk left to implementation details in other controls.
A.8.27 mandates security-by-design principles including data validation/sanitization, distrusting external input, and design reviews against attack patterns, which reaches a minority slice of improper neutralization (e.g. via secure architecture and hardening) but leaves most instances of missing or incorrect escaping in downstream components unaddressed.
Secure coding standards require proper escaping and neutralization of control characters before downstream processing.