CVE-2024-39937: Path Traversal
Source CVE Database V5
Not known to be exploited · CVSS 8.6 High.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 58% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AC:L/AV:N/A:N/C:H/I:N/PR:N/S:C/UI:NExploitation evidence
Disclosed: evidence found.
CVE published 4 Jul 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
AI-suggested
1. Immediately restrict access to the api/image/download endpoint via network controls such as firewalls or API gateways to trusted IPs only. 2. Implement strict input validation and sanitization on the fileName parameter to disallow directory traversal sequences (e.g., ../). 3. Employ web application firewalls (WAFs) with rules to detect and block directory traversal attempts targeting this endpoint. 4. Monitor server logs for unusual file access patterns or requests containing traversal strings. 5. Conduct a thorough audit of all supOS 5.0 instances within the organization to identify vulnerable deployments. 6. If possible, isolate vulnerable systems from critical networks until a patch or official fix is available. 7. Engage with supOS vendors or community to obtain or request patches addressing this vulnerability. 8. Educate security teams about this vulnerability and prepare incident response plans for potential exploitation scenarios. 9. Consider deploying file integrity monitoring to detect unauthorized access or changes to sensitive files.
Description
supOS 5.0 allows api/image/download?fileName=../ directory traversal for reading files.