Skip to content
Fencer Intel
medium 6.4

CVE-2024-37900 json

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

published 2y ago modified 4mo ago also EUVD-2024-2435 , GHSA-wf3x-jccf-5g5g

cvss
6.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
15.8%
EPSS 15.8% chance of exploitation in 30 days, percentile 96%
public exploits
0
none known

Summary

XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. 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. This has been patched in XWiki 14.10.21, 15.5.5, 15.10.6 and 16.0.0.

Patch / fix

  • maven org.xwiki.platform:xwiki-platform-web-war 14.10.21, 15.5.5, 15.10.6, 16.0.0
  • xwiki xwiki 14.10.21, 15.5.5, 15.10.6, 16.0.0

Is CVE-2024-37900 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
2y ago

Exploit prediction

15.80% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

  • jira.xwiki.org https://jira.xwiki.org/browse/XWIKI-19602 referenced PoC, tagged "exploit" by a source, unverified
  • jira.xwiki.org https://jira.xwiki.org/browse/XWIKI-19611 referenced PoC, tagged "exploit" by a source, unverified
  • jira.xwiki.org https://jira.xwiki.org/browse/XWIKI-21769 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 6.4 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N
GitHub 3.1 6.4 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N
NVD 3.1 4.6 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
maven org.xwiki.platform:xwiki-platform-web-war
>=4.2-milestone-3, <14.10.21
>=15.0-rc-1, <15.5.5
>=15.6-rc-1, <15.10.6
>=16.0.0-rc-1, <16.0.0
14.10.21
15.5.5
15.10.6
16.0.0

Affected products

  • xwiki xwiki-platform
  • xwiki xwiki

Classification

Weakness
  • CWE-96 Improper Neutralization of Directives in Statically Saved Code
  • CWE-94 Improper Control of Generation of Code

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.