Skip to main content
VulnerabilityPublished Updated

CVE-2024-31487: Fortinet FortiSandbox · Information Disclosure

Affects Fortinet FortiSandboxSource CVE Database V5

0

Public exploit available · CVSS 5.8 Medium.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score
5.8Medium
How severe the flaw is on the 0–10 CVSS scale.
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/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N/E:F/RL:X/RC:X

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Apr 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Fortinet FortiSandboxAffected
  • 2.4.0 – 4.4.0
8 affected builds
Fixed in–

AI-suggested

  1. Apply official patches or updates from Fortinet as soon as they become available to address CVE-2024-31487.
  2. Until patches are released, restrict network access to FortiSandbox management and HTTP interfaces using firewall rules or network segmentation to limit exposure to trusted administrators only.
  3. Implement strict access controls and monitor HTTP request logs on FortiSandbox devices for unusual or suspicious path traversal attempts.
  4. Employ web application firewalls (WAFs) or intrusion detection/prevention systems (IDS/IPS) to detect and block crafted HTTP requests attempting path traversal.
  5. Regularly audit FortiSandbox configurations and file permissions to minimize sensitive data exposure.
  6. Educate security teams about this vulnerability and incorporate checks for similar path traversal patterns in threat hunting activities.
  7. Consider isolating FortiSandbox appliances in dedicated network segments with limited connectivity to reduce attack surface.
  8. Maintain up-to-date asset inventories to ensure all affected FortiSandbox versions are identified and remediated promptly.

Description

A improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet FortiSandbox 4.4.0 through 4.4.4, FortiSandbox 4.2.1 through 4.2.6, FortiSandbox 4.0 all versions, FortiSandbox 3.2 all versions, FortiSandbox 3.1 all versions, FortiSandbox 3.0 all versions, FortiSandbox 2.5 all versions, FortiSandbox 2.4 all versions allows attacker to information disclosure via crafted http requests.

References

Community reviews

Loading reviews…