CVE-2024-39332: webswing · Path Traversal
Affects webswingSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 1.2% chance of exploitation in 30 days – higher than 69% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 31 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mavenorg.webswing/webswingpkg:maven/org.webswing/webswingOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-39332, organizations should immediately identify all instances of Webswing 23.2.2 in their environment. Implement strict input validation and sanitization on client-supplied data where possible, especially JavaScript code, to prevent path traversal sequences. Employ application-layer firewalls or runtime application self-protection (RASP) solutions to detect and block suspicious path traversal attempts. Monitor server logs and network traffic for unusual file modification activities or unexpected shell script changes. Segregate Webswing servers from critical infrastructure to contain potential breaches. Once an official patch or update is released by the vendor, apply it promptly. Additionally, conduct thorough security audits and penetration tests focused on Webswing deployments to identify residual risks. Educate developers and administrators about secure coding and configuration practices to prevent similar vulnerabilities in the future.
Description
Webswing 23.2.2 allows remote attackers to modify client-side JavaScript code to achieve path traversal, likely leading to remote code execution via modification of shell scripts on the server.