Security Resilience

CVE-2023-29518

Xwiki ≤ 13.10.11

Public PoC
Published
19 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:L
EPSS Score 0.011 66th percentile
Risk Priority 83 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-29518 is a critical-severity Injection (CWE-74) vulnerability in Xwiki Xwiki. Its CVSS base score is 9.9 (Critical).

Operationally, ranked in the top 34% 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 injection vulnerability (CWE-74) in the default Invitation.InvitationCommon page. Any user with view rights can supply input that bypasses escaping and executes arbitrary Groovy, Python, or Velocity code, resulting in full control of the XWiki installation. The flaw affects all versions prior to the listed fixes and carries a CVSS 3.1 score of 9.9.

An attacker with low-privileged network access can exploit the issue without user interaction to read, modify, or delete arbitrary data and execute system-level commands. Because the vulnerable page is installed by default, the attack surface includes any authenticated user granted basic view rights on a standard deployment.

Official patches are available in XWiki 15.0-rc-1, 14.10.1, 14.4.8, and 13.10.11; the project states there are no known workarounds and recommends immediate upgrade. The associated EPSS score has remained flat at 0.2936 since disclosure, indicating steady but not sharply increasing exploitation interest.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. Any user with view rights can execute arbitrary Groovy, Python or Velocity code in XWiki leading to full access to the XWiki installation.…

more

The root cause is improper escaping of `Invitation.InvitationCommon`. This page is installed by default. The vulnerability has been patched in XWiki 15.0-rc-1, 14.10.1, 14.4.8, and 13.10.11. Users are advised to upgrade. There are no known workarounds for this issue.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-29524Same product: Xwiki Xwiki
CVE-2023-29527Same product: Xwiki Xwiki
CVE-2023-36469Same product: Xwiki Xwiki
CVE-2023-29516Same product: Xwiki Xwiki
CVE-2023-36470Same product: Xwiki Xwiki
CVE-2023-29519Same product: Xwiki Xwiki
CVE-2023-29525Same product: Xwiki Xwiki
CVE-2023-29522Same product: Xwiki Xwiki
CVE-2023-29510Same product: Xwiki Xwiki
CVE-2023-29512Same product: Xwiki Xwiki

Affected Assets

xwiki
xwiki
≤ 13.10.11 · 14.0 — 14.4.8 · 14.5 — 14.10.1

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.

addresses: CWE-74

Developer assessments and testing (including injection-focused techniques) identify improper neutralization of special elements, and the verifiable flaw remediation corrects them pre-deployment.

addresses: CWE-74

Identifies indicators of injection attacks (command, SQL, LDAP, etc.) via anomaly and attack monitoring.

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.15 Logging partial match
finds

Logging supports detection of injection attempts but does not prevent the weakness.

finds

Monitoring activities can identify active injection attacks after they occur.

blocks

A.8.25 mandates a secure SDLC process that includes secure coding guidelines, security requirements, checkpoints, testing (scans/penetration), and developer training to reduce injection flaws, but does not itself enforce or guarantee neutralization of special elements at runtime.

blocks

Application security requirements explicitly call for controls against injection attacks in software design.

blocks

A.8.27 mandates security-by-design principles (including distrust external input, data validation/sanitization, secure architecture layers, and design reviews against attack patterns) that reach injection when applied to output construction; this stops exploitation for a minority slice (e.g. where principles drive sanitization) but leaves most code-level injection defects untouched without further implementation rigor.

prevents

Secure coding standards require proper neutralization of special elements, directly addressing CWE-74.

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-74, a class-level weakness, and none of its children carries one either.

References