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). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-29214 is a critical-severity Eval Injection (CWE-95) vulnerability in Xwiki. Its CVSS base score is 9.9 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 31% 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 a code-injection vulnerability in the IncludedDocuments panel. The flaw stems from improper escaping of included pages, which permits any user holding edit rights to inject and execute arbitrary Groovy, Python, or Velocity code. Successful exploitation grants the attacker complete control over the XWiki installation, corresponding to a CVSS 3.1 score of 9.9 and the weaknesses catalogued under CWE-94 and CWE-95.
An authenticated attacker with edit privileges can therefore achieve full confidentiality, integrity, and availability impact on the affected XWiki instance without user interaction. The attack is performed remotely over the network by crafting malicious page content that is rendered through the vulnerable panel.
The issue was corrected in the commits referenced in the GitHub Security Advisory GHSA-qx9h-c5v6-ghqh and tracked under XWIKI-20306; the fixes were released in XWiki 14.4.7 and 14.10. Administrators are advised to upgrade to one of these patched versions.
EPSS scores have remained low, with a current value of 0.0647 and a modest peak of 0.0728, indicating limited observed exploitation interest to date.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-1384
Vulnerability Data
XWiki Commons are technical libraries common to several other top level XWiki projects. Any user with edit rights can execute arbitrary Groovy, Python or Velocity code in XWiki leading to full access to the XWiki installation. The root cause is…
more
improper escaping of the included pages in the IncludedDocuments panel. The problem has been patched on XWiki 14.4.7, and 14.10.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.3.1V1.3.2
Likely Mitigating Controls
Our mappings. 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.
Makes persistent code injection into loaded programs impossible when the executable image itself resides on hardware-protected read-only media.
Dynamically generated code can be produced and executed inside the isolated chamber, preventing host compromise from code-injection payloads.
Validates inputs used in dynamic code generation to block injected directives.
Directly prevents execution of attacker-supplied code written into data memory regions.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Secure SDLC practices directly require input neutralization and avoidance of unsafe dynamic evaluation.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
A.8.29's programme of code review, static analysis, dynamic testing and penetration testing is the complete pre-production discovery set for code injection: eval/dynamic-execution sinks are visible to SAST, code review catches them, and penetration testing reaches the externally exploitable instances, with no nameable remainder.
Training teaches developers the dangers of eval() with untrusted input and safer alternatives (e.g., ast.literal_eval), so a minority of instances are avoided, but the practice is fallible and the weakness is introduced at code-writing time where many other factors compete, matching the A.8.28 -> CWE-79 / CWE-502 partial rung.
Secure coding explicitly requires neutralization of input before dynamic evaluation, directly mitigating eval injection.
A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses like code injection in delivered code the way those practices do, at `partial` -- the effect depends on the supplier's faithful implementation of those practices, which is fallible, and the clause sits at its declared ceiling of `partial` on this verb.
A.8.8's reach is published advisories and component inventory; eval injection does surface as CVEs (so not `none`), but the bulk of CWE-95 instances live in first-party code that nobody published an advisory about, which A.8.8's neighbour A.8.29 reaches and A.8.8 does not.