Security Resilience

CVE-2023-29212

RCE in Xwiki 14.0 – 14.4.7

Public PoCRCE
Published
16 April 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 9.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS Score 0.012 69th percentile
Risk Priority 76 floored blend · peak EPSS

CVSS 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-29212 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 technical libraries shared across multiple XWiki projects, contain a code injection vulnerability that allows any user with edit rights to execute arbitrary Groovy, Python, or Velocity code. The flaw stems from improper escaping of included pages within the included documents edit panel, which grants the attacker full access to the XWiki installation. The issue affects versions prior to the listed patches and carries a CVSS score of 9.9 with CWE-94 and CWE-95 classifications.

An authenticated attacker with edit permissions can supply malicious content that bypasses escaping controls, resulting in remote code execution on the server and complete compromise of the XWiki instance. No special user interface interaction or elevated privileges beyond standard edit rights are required for exploitation.

The GitHub security advisory and associated commits indicate that the vulnerability was addressed in XWiki 14.4.7 and 14.10, with the fix centered on proper escaping of included pages in the edit panel. Administrators are advised to upgrade to these or later releases to eliminate the exposure.

The EPSS score remains low, with a current value of 0.0774 and a peak of 0.0847, showing no material increase that would indicate emerging exploitation interest after disclosure.

OWASP Top 10 for Web (2025)

EU & UK References

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 included documents edit 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

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1559.003 XPC Services Execution
Adversaries can provide malicious content to an XPC service daemon for local code execution.
T1584.008 Network Devices Resource Development
Adversaries may compromise third-party network devices that can be used during targeting.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-26477Same product: Xwiki Xwiki
CVE-2023-29209Same product: Xwiki Xwiki
CVE-2023-29509Same product: Xwiki Xwiki
CVE-2024-31465Same product: Xwiki Xwiki
CVE-2023-29214Same product: Xwiki Xwiki
CVE-2023-35150Same product: Xwiki Xwiki
CVE-2023-50723Same product: Xwiki Xwiki
CVE-2023-46731Same product: Xwiki Xwiki
CVE-2023-40177Same product: Xwiki Xwiki
CVE-2025-24893Same product: Xwiki Xwiki

Affected Assets

xwiki
xwiki
14.10 · 14.0 — 14.4.7

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.3.1
  • V1.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.

addresses: CWE-94

Makes persistent code injection into loaded programs impossible when the executable image itself resides on hardware-protected read-only media.

addresses: CWE-94

Dynamically generated code can be produced and executed inside the isolated chamber, preventing host compromise from code-injection payloads.

addresses: CWE-94

Validates inputs used in dynamic code generation to block injected directives.

addresses: CWE-94

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.

PR.PS-06 mostly match
blocks

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.

finds

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.

prevents

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.

prevents

Secure coding explicitly requires neutralization of input before dynamic evaluation, directly mitigating eval injection.

prevents

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.

finds

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.

References