VulnerabilityPublished 10 Mar 2026Updated 12 Mar 2026

CVE-2026-25972: Fortinet FortiSIEM · Execute Unauthorized Code or Commands

Affects Fortinet FortiSIEMSource CVE Database V5

Compare

Public exploit available · CVSS 4.1 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

4.1Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 28% 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:N/I:L/A:N/E:P/RL:U/RC:C

Base metrics

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

Temporal metrics

Exploit Code Maturity: Proof-of-Concept
Remediation Level: Unavailable
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: None: There is no loss of confidentiality within 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: Proof-of-Concept: Proof-of-concept exploit code is available, or an attack demonstration is not practical for most systems. The code or technique is not functional in all situations and may require substantial modification by a skilled attacker.
Remediation Level: Unavailable: There is either no solution available or it is impossible to apply.
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 10 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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
FortinetFortiSIEM	Affected >=7.3.0 <=7.3.4 =7.4.0	Fixed in–

CPE configurations (6)

cpe:2.3:a:fortinet:fortisiem:7.4.0:*:*:*:*:*:*:*
cpe:2.3:a:fortinet:fortisiem:7.3.4:*:*:*:*:*:*:*
cpe:2.3:a:fortinet:fortisiem:7.3.3:*:*:*:*:*:*:*
cpe:2.3:a:fortinet:fortisiem:7.3.2:*:*:*:*:*:*:*
cpe:2.3:a:fortinet:fortisiem:7.3.1:*:*:*:*:*:*:*
cpe:2.3:a:fortinet:fortisiem:7.3.0:*:*:*:*:*:*:*

AI-suggested

Apply official patches from Fortinet as soon as they become available to address the vulnerability directly.
In the absence of patches, implement strict input validation and sanitization on all web interface parameters to neutralize potentially malicious input.
Deploy web application firewalls (WAFs) with robust XSS detection and blocking capabilities to intercept and prevent exploitation attempts.
Educate users and administrators about the risks of clicking on unsolicited or suspicious URLs, emphasizing caution with links received via email or messaging platforms.
Monitor FortiSIEM logs and network traffic for unusual activities that may indicate exploitation attempts or social engineering campaigns.
Restrict access to the FortiSIEM web interface to trusted networks or VPNs to reduce exposure to remote attackers.
Regularly review and update security policies related to web application security and incident response to incorporate lessons learned from this vulnerability.
Consider implementing Content Security Policy (CSP) headers to limit the execution of untrusted scripts within the FortiSIEM web interface.

Description

An improper neutralization of input during web page generation ('cross-site scripting') vulnerability in Fortinet FortiSIEM 7.4.0, FortiSIEM 7.3.0 through 7.3.4 may allow a remote unauthenticated attacker to provide arbitrary data enabling a social engineering attack via spoofed URL parameters.

Impact

The primary impact of CVE-2026-25972 is on the integrity of affected FortiSIEM systems. Successful exploitation allows attackers to execute arbitrary scripts in the context of a user's browser session, potentially leading to session hijacking, unauthorized actions, or delivery of further malicious payloads. While confidentiality and availability are not directly compromised, the ability to manipulate user sessions can facilitate broader attacks, including credential theft or privilege escalation. Organizations relying on FortiSIEM for security event management may experience reduced trust in their monitoring capabilities if attackers exploit this vulnerability to interfere with alerting or reporting. The requirement for user interaction limits the scope somewhat, but targeted phishing campaigns could effectively leverage this flaw. The lack of known exploits in the wild reduces immediate risk but does not eliminate the potential for future attacks. Overall, the vulnerability poses a moderate risk to organizations with FortiSIEM deployments, particularly those in sensitive sectors such as government, finance, and critical infrastructure.

References

fortiguard.fortinet.com/psirt/FG-IR-26-077 (opens in a new tab)

Community reviews

Loading reviews…