Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2024-21650 is a critical-severity Eval Injection (CWE-95) vulnerability in Xwiki Xwiki. Its CVSS base score is 10.0 (Critical).
Operationally, 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 SI-10 (Information Input Validation) and SI-2 (Flaw Remediation) — 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
- 🇪🇺 ENISA EUVD: EUVD-2024-0417
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
Likely ATT&CK TechniquesAI
Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly requires validation of all inputs, which would block the unsanitized first/last-name payloads that trigger RCE during guest registration.
Mandates prompt installation of security-relevant patches, exactly the XWiki 14.10.17/15.5.3/15.8 RC1 releases that close the input-validation flaw.
Requires control over account creation and registration processes, allowing the organization to disable or restrict guest self-registration that enables the unauthenticated exploit.
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 avoidance of unsafe dynamic evaluation.
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.
Security testing in development can detect eval injection vulnerabilities before deployment.
Secure development life cycle mandates input validation and safe coding practices that directly prevent eval injection.
Application security requirements include rules against dynamic code execution of untrusted input.
Secure architecture principles discourage unsafe dynamic evaluation constructs.
Secure coding explicitly requires neutralization of input before dynamic evaluation, directly mitigating eval injection.
Separation of environments limits the blast radius if eval injection occurs in non-production.