VulnerabilityPublished 10 Sep 2024Updated 14 Jan 2026

CVE-2024-31490: Fortinet FortiSandbox · Information Disclosure

Affects Fortinet FortiSandboxSource CVE Database V5

Public exploit available · CVSS 4.2 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

4.2Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N/E:F/RL:X/RC:X

Base metrics

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Temporal metrics

Exploit Code Maturity: Functional

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.
Exploit Code Maturity: Functional: Functional exploit code is available. The code works in most situations where the vulnerability exists.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Sep 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Fortinet FortiSandbox	Affected 3.1.5 – 4.4.0 5 affected builds	Fixed in–

AI-suggested

Immediately restrict network access to FortiSandbox management interfaces, allowing only trusted administrative IP addresses to connect via HTTP/HTTPS.
Implement strict firewall rules and network segmentation to isolate FortiSandbox appliances from untrusted networks and limit exposure.
Monitor FortiSandbox HTTP logs for unusual GET requests or access patterns that could indicate exploitation attempts.
Apply vendor patches or updates as soon as they become available to remediate the vulnerability.
Use multi-factor authentication and strong credentials for FortiSandbox administrative access to reduce risk from compromised accounts.
Conduct regular vulnerability scans and penetration tests focusing on FortiSandbox appliances to detect potential weaknesses.
Educate security teams about this vulnerability to ensure rapid detection and response to any suspicious activity related to FortiSandbox.
Consider deploying web application firewalls (WAF) or intrusion detection/prevention systems (IDS/IPS) to detect and block malicious HTTP requests targeting FortiSandbox.

Description

An exposure of sensitive information to an unauthorized actor 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.2 through 3.2.4, FortiSandbox 3.1.5 allows attacker to information disclosure via HTTP get requests.

Impact

For European organizations, the exposure of sensitive information from FortiSandbox could lead to increased risk of targeted attacks, including lateral movement and privilege escalation, if attackers leverage disclosed data. Organizations relying on FortiSandbox for malware analysis and threat detection may have their internal threat intelligence and sandboxed data exposed, undermining security posture. Critical infrastructure sectors, financial institutions, and large enterprises using FortiSandbox appliances are particularly at risk due to the sensitive nature of the data processed. While the vulnerability does not directly compromise system integrity or availability, the confidentiality breach could facilitate more sophisticated attacks, data theft, or espionage. The medium severity rating indicates a moderate but non-negligible risk, especially in environments where FortiSandbox is exposed to less trusted networks or insufficiently segmented. The lack of known exploits reduces immediate risk but does not eliminate the threat, as attackers may develop exploits based on the disclosed vulnerability details.

References

fortiguard.com/psirt/FG-IR-24-051 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Jan 2026, 14:18 UTC

Technical details

References

Community reviews

Related threats