Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-wf3x-jccf-5g5g

MEDIUM

GHSA-wf3x-jccf-5g5g is a medium-severity (CVSS 6.4) CWE-96 vulnerability in org.xwiki.platform:xwiki-platform-web-war. 3 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-wf3x-jccf-5g5g is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

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

Also known asCVE-2024-37900
Published
Jul 31, 2024
Updated
Nov 18, 2024
Affected
4 pkgs
Patched
4 / 4
Exploits
3 known

Blast Radius

4 pkgs affected
org.xwiki.platform:xwiki-platform-web-warorg.xwiki.platform:xwiki-platform-web-warorg.xwiki.platform:xwiki-platform-web-warorg.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
EcosystemPackageVulnerable rangeFix
Mavenorg.xwiki.platform:xwiki-platform-web-war4.2-milestone-3&&< 14.10.2114.10.21
Mavenorg.xwiki.platform:xwiki-platform-web-war15.0-rc-1&&< 15.5.515.5.5
Mavenorg.xwiki.platform:xwiki-platform-web-war15.6-rc-1&&< 15.10.615.10.6
Mavenorg.xwiki.platform:xwiki-platform-web-war16.0.0-rc-1&&< 16.0.016.0.0
Exploits & PoCs
3

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

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-web-war. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. 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 GHSA-wf3x-jccf-5g5g is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-wf3x-jccf-5g5g is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-wf3x-jccf-5g5g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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
O3 Security · Impact-Aware SCA

Is GHSA-wf3x-jccf-5g5g in your dependencies?

O3 detects GHSA-wf3x-jccf-5g5g across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.