How severe is CVE-2024-37900?

CVE-2024-37900 has a CVSS score of 6.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2024-37900?

CVE-2024-37900 affects the following packages: org.xwiki.platform:xwiki-platform-web-war (Maven), org.xwiki.platform:xwiki-platform-web-war (Maven), org.xwiki.platform:xwiki-platform-web-war (Maven), org.xwiki.platform:xwiki-platform-web-war (Maven). Ecosystems affected: Maven.

How do I fix CVE-2024-37900?

Update org.xwiki.platform:xwiki-platform-web-war to 14.10.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-37900 is resolved across your whole dependency graph.

How do I detect CVE-2024-37900 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-web-war, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-37900 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2024-37900 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2024-37900, including 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2024-37900?

CVE-2024-37900 has an EPSS (Exploit Prediction Scoring System) score of 15.8%, placing it in the 97th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2024-37900?

CVE-2024-37900 is classified as CWE-96 (CWE-96), Code Injection (CWE-94). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2024-37900 published, and has it been updated?

CVE-2024-37900 was published on July 31, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2024-37900 — xwiki-platform-web-war

MEDIUMFix: xwiki/xwiki-platform@6cdd69d

CVE-2024-37900 is a medium-severity (CVSS 6.4) CWE-96 vulnerability in org.xwiki.platform:xwiki-platform-web-war. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.xwiki.platform:xwiki-platform-web-war — see the affected versions and patch details below.

XWiki Platform vulnerable to Cross-site Scripting through attachment filename in uploader

Also known asGHSA-wf3x-jccf-5g5g

Published

Jul 31, 2024

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

3 known

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-37900.

EPSS Exploitation Probability

via FIRST.org ↗

15.8%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

☕org.xwiki.platform:xwiki-platform-web-war☕org.xwiki.platform:xwiki-platform-web-war☕org.xwiki.platform:xwiki-platform-web-war☕org.xwiki.platform:xwiki-platform-web-war

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Patches

This has been patched in XWiki 14.10.21, 15.5.5, 15.10.6 and 16.0.0.

Workarounds

We're not aware of any workaround except upgrading.

References

Attribution

This vulnerability has been independently reported by Aleksey Solovev (Positive Technologies) and Georgios Roumeliotis for TwelveSec.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-web-war`	≥ 4.2-milestone-3&&< 14.10.21	14.10.21`org.xwiki.platform:xwiki-platform-web-war:14.10.21`
☕Maven	`org.xwiki.platform:xwiki-platform-web-war`	≥ 15.0-rc-1&&< 15.5.5	15.5.5`org.xwiki.platform:xwiki-platform-web-war:15.5.5`
☕Maven	`org.xwiki.platform:xwiki-platform-web-war`	≥ 15.6-rc-1&&< 15.10.6	15.10.6`org.xwiki.platform:xwiki-platform-web-war:15.10.6`
☕Maven	`org.xwiki.platform:xwiki-platform-web-war`	≥ 16.0.0-rc-1&&< 16.0.0	16.0.0`org.xwiki.platform:xwiki-platform-web-war:16.0.0`

Affected Products

1 product · 6 configurations

Application

xwikixwiki

≥ 15.6 && < 15.10.6

2 versions

4.216.0.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

XWiki Platform is a generic wiki platform offering runtime services for …

jira.xwiki.orgNVDSep 2024

Report on jira.xwiki.org

jira.xwiki.orgNVDSep 2024

Report on jira.xwiki.org

jira.xwiki.orgNVDSep 2024

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-web-war, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-web-war to 14.10.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-37900 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

### 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 p