Summary
XWiki Platform vulnerable to Cross-site Scripting through attachment filename in uploader
Workarounds
We're not aware of any workaround except upgrading.
References
- https://jira.xwiki.org/browse/XWIKI-19611
- https://jira.xwiki.org/browse/XWIKI-21769
- https://jira.xwiki.org/browse/XWIKI-19602
- https://github.com/xwiki/xwiki-platform/commit/910a5018a50039e8b24556573dfe342f143ef949
Attribution
This vulnerability has been independently reported by Aleksey Solovev (Positive Technologies) and Georgios Roumeliotis for TwelveSec.
Impact
When uploading an attachment with a malicious filename, malicious JavaScript code could be executed. This requires a social engineering attack to get the victim into uploading a file with a malicious name. The malicious code is solely executed during the upload and affects only the user uploading the attachment. While this allows performing actions in the name of that user, it seems unlikely that a user wouldn't notice the malicious filename while uploading the attachment.
In order to reproduce, as any user, create a file named "><img src=1 onerror=alert(1)>.jpg. Then go to any page where you have edit rights and upload the file in the attachments tab. If alerts appear and display "1", then the instance is vulnerable.
Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.
CVE-2024-37900 has a CVSS score of 6.4 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (14.10.21, 15.5.5, 15.10.6, 16.0.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
This has been patched in XWiki 14.10.21, 15.5.5, 15.10.6 and 16.0.0.
Frequently Asked Questions
- What is CVE-2024-37900? CVE-2024-37900 is a high-severity code injection vulnerability in org.xwiki.platform:xwiki-platform-web-war (maven), affecting versions >= 4.2-milestone-3, < 14.10.21. It is fixed in 14.10.21, 15.5.5, 15.10.6, 16.0.0. Untrusted input is evaluated as executable code within the application's runtime environment.
- How severe is CVE-2024-37900? CVE-2024-37900 has a CVSS score of 6.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of org.xwiki.platform:xwiki-platform-web-war are affected by CVE-2024-37900? org.xwiki.platform:xwiki-platform-web-war (maven) versions >= 4.2-milestone-3, < 14.10.21 is affected.
- Is there a fix for CVE-2024-37900? Yes. CVE-2024-37900 is fixed in 14.10.21, 15.5.5, 15.10.6, 16.0.0. Upgrade to this version or later.
- Is CVE-2024-37900 exploitable, and should I be worried? Whether CVE-2024-37900 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2024-37900 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2024-37900?
- Upgrade
org.xwiki.platform:xwiki-platform-web-warto 14.10.21 or later - Upgrade
org.xwiki.platform:xwiki-platform-web-warto 15.5.5 or later - Upgrade
org.xwiki.platform:xwiki-platform-web-warto 15.10.6 or later - Upgrade
org.xwiki.platform:xwiki-platform-web-warto 16.0.0 or later
- Upgrade