CVE-2025-54353VulnerabilityPublished 9 Dec 2025Updated 14 Jan 2026

CVE-2025-54353: Fortinet FortiSandbox · Execute unauthorized code or commands

Affects Fortinet FortiSandboxSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.3Medium

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

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

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

Base metrics

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

Temporal metrics

Exploit Code Maturity: Functional
Report Confidence: Confirmed

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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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.
Report Confidence: Confirmed: Detailed reports exist, or functional reproduction is possible (functional exploits may provide this). Source code is available to independently verify the assertions of the research, or the author or vendor of the affected code has confirmed the presence of the vulnerability.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Dec 2025
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 2026-10-26.

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 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 =5.0.0 =4.4.0 =4.2.1 =4.0.0	Fixed in–

AI-suggested

1. Monitor Fortinet advisories closely and apply official patches or updates as soon as they become available to address CVE-2025-54353. 2. Implement strict input validation and output encoding on all web interfaces to prevent injection of malicious scripts. 3. Deploy Web Application Firewalls (WAFs) with rules specifically designed to detect and block XSS attack patterns targeting FortiSandbox management portals. 4. Restrict access to FortiSandbox web interfaces to trusted networks and VPNs, minimizing exposure to untrusted users. 5. Enforce multi-factor authentication (MFA) for all administrative access to FortiSandbox to reduce risk from compromised credentials. 6. Conduct user training to recognize phishing attempts and suspicious links that could trigger the vulnerability. 7. Regularly audit FortiSandbox logs and monitor for unusual activity indicative of exploitation attempts. 8. Consider network segmentation to isolate FortiSandbox appliances from general user networks to limit attack surface. 9. If possible, disable or limit unnecessary web interface features that process user input. 10. Prepare incident response plans that include scenarios involving FortiSandbox compromise.

Description

An Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability [CWE-79] vulnerability in Fortinet FortiSandbox 5.0.0 through 5.0.2, FortiSandbox 4.4.0 through 4.4.7, FortiSandbox 4.2 all versions, FortiSandbox 4.0 all versions may allow an attacker to perform an XSS attack via crafted HTTP requests.

Impact

For European organizations, the vulnerability poses a moderate risk primarily to the confidentiality and integrity of FortiSandbox management sessions and data. Successful exploitation could enable attackers to execute unauthorized commands or scripts, potentially leading to unauthorized access or manipulation of sandboxed files and threat analysis results. This could undermine the effectiveness of threat detection and response capabilities, increasing the risk of undetected malware propagation or data leakage. Organizations in sectors such as finance, telecommunications, energy, and government that rely on FortiSandbox for advanced threat protection may face increased exposure. The lack of availability impact reduces immediate operational disruption risk, but the potential for stealthy compromise remains significant. The requirement for user interaction means phishing or social engineering could be used to trigger the attack, emphasizing the need for user awareness. The absence of known exploits in the wild currently lowers immediate threat but does not eliminate future risk, especially as exploit code could be developed following public disclosure.

References

fortiguard.fortinet.com/psirt/FG-IR-25-477 (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:46 UTC

Technical details

References

Community reviews

Related threats