dbcve.org
FortisiemApplication · Fortinet

CVE-2025-25256

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 6.7.10 / 7.0.4 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An improper neutralization of special elements used in an OS command ('OS Command Injection') vulnerability [CWE-78] vulnerability in Fortinet FortiSIEM 7.3.0 through 7.3.1, FortiSIEM 7.2.0 through 7.2.5, FortiSIEM 7.1.0 through 7.1.7, FortiSIEM 7.0.0 through 7.0.3, FortiSIEM 6.7.0 through 6.7.9, FortiSIEM 6.6 all versions, FortiSIEM 6.5 all versions, FortiSIEM 6.4 all versions, FortiSIEM 6.3 all versions, FortiSIEM 6.2 all versions, FortiSIEM 6.1 all versions, FortiSIEM 5.4 all versions, FortiSIEM 5.3 all versions, FortiSIEM 5.2 all versions, FortiSIEM 5.1 all versions, FortiSIEM 5.0 all versions, FortiSIEM 4.10 all versions, FortiSIEM 4.9 all versions, FortiSIEM 4.7 all versions allows an unauthenticated attacker to execute unauthorized code or commands via crafted CLI requests.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

FortiSIEM contains an OS command injection vulnerability (CWE-78) in its CLI interface. Unauthenticated attackers can send specially crafted CLI requests containing malicious OS commands that get executed with the privileges of the underlying service, potentially leading to complete system compromise.

MitigationUpgrade FortiSIEM to version 7.3.2, 7.2.6, 7.1.8, 7.0.4, 6.7.9 or later per Fortinet's advisory. If immediate patching is not possible, restrict network access to the CLI management interface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FortisiemApplication
Affected:>= 5.4.0, < 6.7.10>= 7.0.0, < 7.0.4>= 7.1.0, < 7.1.8>= 7.2.0, < 7.2.6>= 7.3.0, < 7.3.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if FortiSIEM is installed
    Run 'phstatus' or check for FortiSIEM processes via 'ps -ef | grep -i fortisiem' or look for FortiSIEM installation directories such as /opt/phoenix or /fortisiem
    Affected if FortiSIEM is not found on the system, the system is not affected
  2. Determine the installed FortiSIEM version
    Run 'phver' from the CLI or check the web UI under Admin > System > General > Version
    Affected if Unable to retrieve version information - manual verification may be required
  3. Compare version against affected ranges
    Check if the installed version falls within any of these ranges: 5.4.0 to 6.7.9, 7.0.0 to 7.0.3, 7.1.0 to 7.1.7, 7.2.0 to 7.2.5, or 7.3.0 to 7.3.1
    Affected if Version is within any of the affected ranges listed above - the system is vulnerable to CVE-2025-25256
  4. Verify CLI management interface network exposure
    Check firewall rules or network access controls for port 22 (SSH) or any port serving the FortiSIEM CLI management interface. Review configuration files in /opt/phoenix/config/phoenix_config.txt for 'listen' or 'interface' settings
    Affected if CLI management interface is accessible from untrusted networks - combined with a vulnerable version, this creates an exploitable condition

The environment is affected if FortiSIEM is installed with a version matching any of the affected ranges (5.4.0-6.7.9, 7.0.0-7.0.3, 7.1.0-7.1.7, 7.2.0-7.2.5, or 7.3.0-7.3.1) AND the CLI management interface is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.7.10 / 7.0.4 / 7.1.8 or later
Fixed in 6.7.107.0.47.1.8
Interim mitigation

Upgrade FortiSIEM to version 7.3.2, 7.2.6, 7.1.8, 7.0.4, 6.7.9 or later per Fortinet's advisory. If immediate patching is not possible, restrict network access to the CLI management interface.

Recommended fix High confidence

Upgrade to 6.7.10, 7.0.4, 7.1.8, or 7.2.6 depending on your current branch - these are the minimum fixed versions

  1. Identify your current FortiSIEM version using the CLI command 'phoenixservers.sh --status' or through the FortiSIEM web UI under Admin > System Settings > System Info
  2. If running version >= 5.4.0 and < 6.7.10, upgrade to version 6.7.10
  3. If running version >= 7.0.0 and < 7.0.4, upgrade to version 7.0.4
  4. If running version >= 7.1.0 and < 7.1.8, upgrade to version 7.1.8
  5. If running version >= 7.2.0 and < 7.2.6, upgrade to version 7.2.6
  6. After upgrade, verify the system is functioning normally and review audit logs for any suspicious activity
Caveat Point releases typically include backward-compatible fixes; review Fortinet release notes for any configuration changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fortisiem Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-25256 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-25256 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data