Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2025-25256: Unauthenticated OS Command Injection in Fortinet FortiSIEM

Published Aug 12, 2025 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS67.3%99th percentile
CISA KEVNoNot listed
In the wildReported9 exploitation records in Mallory
Vendor
Fortinet
IdentifiersCVE-2025-25256CWE-78 · Improper Neutralization of Special…

CVE-2025-25256 is an OS command injection vulnerability in Fortinet FortiSIEM caused by improper neutralization of special elements in attacker-controlled input. Unauthenticated remote attackers can submit crafted CLI requests to the phMonitor service on TCP port 7900 to execute unauthorized code or operating-system commands. Affected releases include 7.3.0–7.3.1, 7.2.0–7.2.5, 7.1.0–7.1.7, 7.0.0–7.0.3, 6.7.0–6.7.9, and all versions of branches 6.1–6.6, 5.0–5.4, 4.10, 4.9, and 4.7. FortiSIEM 7.4 is not affected. Practical exploit code is publicly available; accounts of confirmed exploitation differ.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation permits remote code or command execution on an affected FortiSIEM system without authentication or user interaction. Potential consequences include full system compromise, sensitive-data theft, and malware deployment. Privilege escalation is also identified as an impact, although the execution privilege level and escalation mechanism specific to this CVE are not consistently established.

Mitigation

If you can’t patch tonight, do this now.

Restrict access to the phMonitor service on TCP port 7900 to trusted internal hosts, particularly while patching is pending. Monitor for unusual system activity, but do not rely on distinctive exploitation indicators: the vendor states that the exploit code does not appear to produce distinctive indicators of compromise.

Remediation

Patch, then assume compromise.

Upgrade to FortiSIEM 7.3.2 or later, 7.2.6 or later, 7.1.8 or later, 7.0.4 or later, or 6.7.10 or later within the respective release branch. Migrate affected older branches to a supported fixed release. FortiSIEM 7.4 is listed as unaffected.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
FortinetFortisiemapplication
FAQ

Frequently asked questions

Is CVE-2025-25256 exploited in the wild?
Yes. As of Oct 10, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2025-25256?
Yes. As of Oct 10, 2026, Mallory has reports of a public exploit for CVE-2025-25256.
Is there a patch for CVE-2025-25256?
Upgrade to FortiSIEM 7.3.2 or later, 7.2.6 or later, 7.1.8 or later, 7.0.4 or later, or 6.7.10 or later within the respective release branch. Migrate affected older branches to a supported fixed release.
What products are affected by CVE-2025-25256?
Fortinet Fortisiem.
How severe is CVE-2025-25256?
CVE-2025-25256 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 67.3% (99th percentile) as of Oct 10, 2026.
Activity feed

Recent activity

130 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+16 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity105Community discussion across Reddit, Mastodon, and other social sources.