Cyber Resilience

CVE-2024-21650

RCE in Xwiki ≤ 14.10.17

Public PoCHigh EPSSRCE
Published
08 January 2024
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 10.0
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS Score 0.93 99.8th percentile
Risk Priority 100 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-2024-21650 is a critical-severity Eval Injection (CWE-95) vulnerability in Xwiki Xwiki. Its CVSS base score is 10.0 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique JavaScript (T1059.007); ranked in the top 0.2% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

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 is affected by a remote code execution vulnerability that stems from insufficient input sanitization in its user registration feature. The flaw resides in the handling of the first name and last name fields, where specially crafted payloads can trigger arbitrary code execution on the server. All installations that permit guest registration are impacted, and the issue is tracked under CWE-94 and CWE-95 with a CVSS score of 10.0.

An unauthenticated attacker can exploit the vulnerability simply by completing the self-registration form with malicious content in either name field. Successful exploitation grants the attacker the ability to run arbitrary code within the XWiki runtime, potentially leading to full compromise of the underlying server and any hosted applications.

Official advisories and the linked GitHub security notice recommend upgrading to the patched releases XWiki 14.10.17, 15.5.3, or 15.8 RC1. The corresponding commits that address the input validation gaps are published in the project repository, and administrators are advised to apply the updates promptly or restrict guest registration until patches can be deployed.

The EPSS score currently stands at 0.9254 with a recorded peak of 0.9346, indicating sustained and elevated exploitation interest following disclosure.

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. XWiki is vulnerable to a remote code execution (RCE) attack through its user registration feature. This issue allows an attacker to execute arbitrary…

more

code by crafting malicious payloads in the "first name" or "last name" fields during user registration. This impacts all installations that have user registration enabled for guests. This vulnerability has been patched in XWiki 14.10.17, 15.5.3 and 15.8 RC1.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1059.007 JavaScript Execution
Adversaries may abuse various implementations of JavaScript for execution.
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
T1059.001 PowerShell Execution
Adversaries may abuse PowerShell commands and scripts for execution.
T1059.002 AppleScript Execution
Adversaries may abuse AppleScript for execution.
T1059.004 Unix Shell Execution
Adversaries may abuse Unix shell commands and scripts for execution.
T1059.005 Visual Basic Execution
Adversaries may abuse Visual Basic (VB) for execution.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-35150Same product: Xwiki Xwiki
CVE-2023-40177Same product: Xwiki Xwiki
CVE-2024-31996Same product: Xwiki Xwiki
CVE-2024-31465Same product: Xwiki Xwiki
CVE-2023-29210Same product: Xwiki Xwiki
CVE-2023-50721Same product: Xwiki Xwiki
CVE-2023-29509Same product: Xwiki Xwiki
CVE-2023-35152Same product: Xwiki Xwiki
CVE-2023-37909Same product: Xwiki Xwiki
CVE-2025-24893Same product: Xwiki Xwiki

Affected Assets

xwiki
xwiki
≤ 14.10.17 · 15.0 — 15.5.3 · 15.6 — 15.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

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and code analysis can discover eval-injection flaws but does not stop their introduction.

Input validation explicitly requires neutralizing untrusted data before it reaches dynamic evaluation constructs such as eval.

Least privilege limits the damage an injected code fragment can perform once executed.

Secure-development standards and tools can mandate safe coding patterns that avoid unsafe dynamic evaluation.

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.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input neutralization and avoidance of unsafe dynamic evaluation.

PR.DS-10 none match
prevents

PR.DS-10 protects runtime data confidentiality/integrity but has no bearing on neutralizing externally influenced input during code generation, so neither direction shows any preventive effect.

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.

finds

Security testing in development can detect eval injection vulnerabilities before deployment.

prevents

Secure development life cycle mandates input validation and safe coding practices that directly prevent eval injection.

prevents

Application security requirements include rules against dynamic code execution of untrusted input.

prevents

Secure architecture principles discourage unsafe dynamic evaluation constructs.

prevents

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

References