Cyber Resilience

CVE-2024-41947

XSS in Xwiki 11.8 – 15.10.8

Published
31 July 2024
Modified
06 September 2024
Patch / 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.017 75th percentile
Risk Priority 73 floored blend · peak EPSS

Summary

CVE-2024-41947 is a critical-severity Basic XSS (CWE-80) 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 in the top 25% of CVEs by exploit likelihood; 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 for building applications, contains a cross-site scripting vulnerability tracked as CVE-2024-41947. The flaw allows an attacker to inject and execute JavaScript by deliberately creating an edit conflict against a page being modified by a higher-privileged user, resulting in script execution in that user's browser session and full compromise of the XWiki instance's confidentiality, integrity, and availability. The issue is classified under CWE-79 and CWE-80 and carries a CVSS 3.1 score of 9.0.

An authenticated user with basic editing rights can trigger the attack by forcing a conflict during another user's editing session; the injected JavaScript then runs with the privileges of the targeted higher-rights user, enabling actions such as data exfiltration or privilege escalation across the installation.

The vulnerability has been addressed in the official patches released for XWiki 15.10.8 and 16.3.0RC1, with the fixes documented in the project's GitHub security advisory and corresponding commits that prevent malicious conflict payloads from executing scripts.

The EPSS score remains flat at 0.1301 with no material increase after 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. By creating a conflict when another user with more rights is currently editing a page, it is possible to execute JavaScript snippets on…

more

the side of the other user, which compromises the confidentiality, integrity and availability of the whole XWiki installation. This has been patched in XWiki 15.10.8 and 16.3.0RC1.

CWE(s)

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.
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.
T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
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.
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.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-66472Same product: Xwiki Xwiki
CVE-2022-36097Same product: Xwiki Xwiki
CVE-2023-35153Same product: Xwiki Xwiki
CVE-2023-29508Same product: Xwiki Xwiki
CVE-2023-35157Same product: Xwiki Xwiki
CVE-2022-36094Same product: Xwiki Xwiki
CVE-2022-36096Same product: Xwiki Xwiki
CVE-2025-53835Same product: Xwiki Xwiki
CVE-2023-40176Same product: Xwiki Xwiki
CVE-2023-35162Same product: Xwiki Xwiki

Affected Assets

xwiki
xwiki
11.8 — 15.10.8 · 16.0 — 16.3.0

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
  • V1.2.1
  • V1.3.1

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover missing or incorrect neutralization of script tags through targeted XSS test cases.

Input validation explicitly requires checking and neutralizing untrusted web inputs containing script-related characters before they reach a downstream renderer.

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

Secure engineering principles include mandatory output encoding and neutralization of HTML metacharacters to stop injection at the source.

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 output encoding and input validation that prevent basic XSS.

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.

finds

Security testing in development catches unneutralized script tags before release.

prevents

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

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.

prevents

Secure SDLC mandates input validation and output encoding that directly prevent basic XSS.

prevents

Application security requirements explicitly call for neutralization of script-related HTML tags.

prevents

Secure coding standards require proper escaping of <, >, & to block XSS.

References