Cyber Resilience

CVE-2024-43400

XSS in Xwiki ≤ 14.10.21

XSS
Published
19 August 2024
Modified
20 August 2024
Patch / advisory
View advisory
CVSS Score v3.1 9.0
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
EPSS Score 0.0049 40th percentile
Risk Priority 70 floored blend · peak EPSS

Summary

CVE-2024-43400 is a critical-severity Static Code Injection (CWE-96) vulnerability in Xwiki Xwiki. Its CVSS base score is 9.0 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Browser Session Hijacking (T1185); ranked at the 40th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

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, a generic wiki platform that provides runtime services for applications, is affected by CVE-2024-43400. The flaw allows a user lacking Script or Programming rights to construct a URL that loads a page containing arbitrary JavaScript, corresponding to CWE-96 and CWE-79 weaknesses. The issue carries a CVSS 3.1 score of 9.0 and was disclosed on 2024-08-19.

An attacker can exploit the vulnerability by crafting a malicious URL and using social engineering to induce a victim to visit it. Successful exploitation enables the attacker to execute JavaScript in the context of the target user’s session, potentially achieving high impact on confidentiality, integrity, and availability.

The vulnerability has been addressed in the official patches released for XWiki versions 14.10.21, 15.5.5, 15.10.6, and 16.0.0, as documented in the project’s GitHub security advisory and the linked commit that resolves the underlying issue.

The associated EPSS score remains flat at 0.0727 with no material increase since disclosure.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. It is possible for a user without Script or Programming rights to craft a URL pointing to a page with arbitrary JavaScript. This…

more

requires social engineer to trick a user to follow the URL. This has been patched in XWiki 14.10.21, 15.5.5, 15.10.6 and 16.0.0.

CWE(s)
CWE-96CWE-79

Related Threats

MITRE ATT&CK Enterprise Techniques

T1185 Browser Session Hijacking Collection
Adversaries may take advantage of security vulnerabilities and inherent functionality in browser software to change content, modify user-behaviors, and intercept information as part of various browser session hijacking techniques.
attack.mitre.org →
T1539 Steal Web Session Cookie Credential Access
An adversary may steal web application or service session cookies and use them to gain access to web applications or Internet services as an authenticated user without needing credentials.
attack.mitre.org →
T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
attack.mitre.org →
T1027.009 Embedded Payloads Stealth
Adversaries may embed payloads within other files to conceal malicious content from defenses.
attack.mitre.org →
T1189 Drive-by Compromise Initial Access
Adversaries may gain access to a system through a user visiting a website over the normal course of browsing.
attack.mitre.org →
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.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-40176Same product: Xwiki Xwiki
CVE-2023-35162Same product: Xwiki Xwiki
CVE-2023-34464Same product: Xwiki Xwiki
CVE-2023-29201Same product: Xwiki Xwiki
CVE-2023-29202Same product: Xwiki Xwiki
CVE-2023-26480Same product: Xwiki Xwiki
CVE-2023-29506Same product: Xwiki Xwiki
CVE-2023-29205Same product: Xwiki Xwiki
CVE-2023-35155Same product: Xwiki Xwiki
CVE-2023-29515Same product: Xwiki Xwiki

Affected Assets

xwiki
xwiki
≤ 14.10.21 · 15.0 — 15.5.5 · 15.6 — 15.10.6

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.1.2
  • V1.3.2

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover missing neutralization of directives in saved code artifacts.

SI-10 Information Input Validation good match

Input validation directly stops unneutralized directives from being inserted into static code resources.

SI-15 Information Output Filtering good match

Output filtering can catch or sanitize unneutralized script content before it is served to users.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles include secure input handling and neutralization requirements that structurally avoid static injection.

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 to block static code injection into templates, configs, or libraries.

PR.PS-02 partial match
prevents

Patching and EOL replacement can remediate known XSS instances in libraries or frameworks (partial) but do nothing to enforce input neutralization in application code (none).

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.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance will detect static code injection but does not prevent it at the source.

A.5.6 Contact with special interest groups partial match
prevents

Knowledge exchange on emerging attack techniques and patches reduces the likelihood that cross-site scripting flaws remain unaddressed in deployed applications.

A.5.7 Threat intelligence partial match
prevents

Operational indicators of compromise for web-application attacks can be incorporated into WAF or input-filtering rules, lowering the likelihood that unsanitized data reaches the browser.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and sanitization that directly prevents static code injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements include rules for neutralizing untrusted input before it is stored in executable resources.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce injection surfaces but do not prescribe the specific neutralization techniques.

References