FortisiemApplication · Fortinet
CVE-2025-64155
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 · uneditedAn improper neutralization of special elements used in an os command ('os command injection') vulnerability in Fortinet FortiSIEM 7.4.0, FortiSIEM 7.3.0 through 7.3.4, FortiSIEM 7.1.0 through 7.1.8, FortiSIEM 7.0.0 through 7.0.4, FortiSIEM 6.7.0 through 6.7.10 may allow an attacker to execute unauthorized code or commands via crafted TCP 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 confidenceFortiSIEM contains an OS command injection vulnerability in the TCP request handler. Attackers can send specially crafted TCP packets containing shell metacharacters that get executed by the underlying operating system with the privileges of the FortiSIEM service account, allowing full system compromise.
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
>= 6.7.0, < 7.1.9>= 7.2.0, < 7.2.7>= 7.3.0, < 7.3.5= 7.4.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm FortiSIEM is installedRun command: phpmon -v or cat /opt/phoenix/config/build.info | grep versionAffected if FortiSIEM is present and the version falls within the affected ranges (6.7.0 to 7.1.8, 7.2.0 to 7.2.6, 7.3.0 to 7.3.4, or 7.4.0)
-
Identify FortiSIEM versionCheck the UI under Admin > Setup > System > License, or run: cd /opt/phoenix && ./phoenix -versionAffected if The displayed version matches any of the affected version ranges listed above
-
Verify TCP handler service statusCheck if the TCP listener service is enabled: systemctl status phoenyx or check FortiSIEM GUI > Admin > Settings > Event Management > TCPAffected if The TCP request handler service is running and exposed to network access
-
Check network exposureReview firewall rules or network ACLs: iptables -L -n | grep -E '(50000|50001|50002)' or check FortiSIEM network settings in the GUIAffected if TCP handler ports (typically 50000-50002) are accessible from untrusted networks or the internet
-
Audit for suspicious TCP connectionsReview FortiSIEM logs for unusual TCP requests: grep -i 'command injection' /opt/phoenix/log/phoenix.log or monitor for shell metacharacters in event logsAffected if Unexpected TCP packets containing shell metacharacters (|, ;, $, `, etc.) appear in logs or network captures
A user is affected if FortiSIEM is installed with a version in the vulnerable ranges (6.7.0-7.1.8, 7.2.0-7.2.6, 7.3.0-7.3.4, or 7.4.0) AND the TCP request handler is exposed to network attackers.
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.1.97.2.77.3.5
Upgrade FortiSIEM to the latest available version (7.4.1 or later for 7.4.x, or the latest 7.3.x/7.1.x/7.0.x release that includes the fix). If immediate patching is not possible, restrict network access to FortiSIEM management interfaces to trusted IPs only.
FortiSIEM 7.1.9 or later for 6.7.x; 7.2.7 or later for 7.2.x; 7.3.5 or later for 7.3.x; 7.4.1 or later for 7.4.0
- 1. Identify the current FortiSIEM version by logging into the FortiSIEM web UI or running 'phadmin --version' on the supervisor node
- 2. Determine the appropriate target version based on current version: if 6.7.x upgrade to 7.1.9+, if 7.2.x upgrade to 7.2.7+, if 7.3.x upgrade to 7.3.5+, if 7.4.0 upgrade to 7.4.1+
- 3. Review the FortiSIEM release notes for the target version to understand new features, changes, and any prerequisites
- 4. Create a complete backup of the FortiSIEM configuration and database
- 5. Schedule a maintenance window as upgrades may require downtime
- 6. Download the upgrade file from Fortinet support portal (https://support.fortinet.com)
- 7. Apply the upgrade following Fortinet's documented upgrade procedure for the FortiSIEM supervisor and all workers
- 8. After upgrade completes, verify the FortiSIEM version reflects the target version
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 / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64155 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-64155 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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