CVE-2024-47575: FortiJump
- Vendor
- Fortinet
FortiJump is a missing-authentication vulnerability in the Fortinet FortiManager FGFM daemon (fgfmd) that permits remote unauthenticated attackers to execute arbitrary code or commands through specially crafted management requests. Affected releases include FortiManager 7.6.0, 7.4.0–7.4.4, 7.2.0–7.2.7, 7.0.0–7.0.12, 6.4.0–6.4.14, and 6.2.0–6.2.12; and FortiManager Cloud 7.4.1–7.4.4, 7.2.1–7.2.7, 7.0.1–7.0.12, and 6.4.1–6.4.7. Certain FortiAnalyzer models are also affected when FortiManager functionality and an interface providing the FGFM service are enabled. Exploitation can involve registering a rogue managed device and executing commands to extract sensitive management data. The vulnerability was exploited as a zero-day in 2024 and patched in October 2024.
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 enables system-context code or command execution on the management appliance, allowing installation of programs and access to, modification of, or deletion of data. Observed attacks stole managed-device configurations, network topology, administrative and VPN credentials, certificates, private keys, and other cryptographic trust material. A telecommunications managed service provider intrusion attributed to CL-STA-0954, also known as UNC5820, exposed information associated with more than 500 managed FortiGate firewalls; this exposure did not establish that every associated firewall or customer network was compromised. Recovered credentials and trust material enabled subsequent unauthorized VPN access and management impersonation. Deployment of PEERSTITCH on selected firewalls additionally involved exploitation of the separate vulnerability CVE-2025-61624.
Mitigation
If you can’t patch tonight, do this now.
Restrict FGFM access, normally TCP port 541, to authorized FortiGate peers and dedicated management networks, including protection against access through compromised internal systems. Pending patching, FortiManager 7.0.12+, 7.2.5+, and 7.4.3+, excluding 7.6.0, can enable 'fgfm-deny-unknown' under 'config system global' to block unknown-device registration; this is the only recommended workaround for FortiManager Cloud. This also blocks legitimate devices whose serial numbers are absent from the device list. Where applicable, disable unregistered log-device detection and set 'unreg-dev-option ignore' for FortiGate Updates or Web Filtering. FortiManager 7.2.0+ can alternatively use local-in policies permitting only authorized source addresses on port 541. Another workaround, supported in 7.2.2+, 7.4.0+, and 7.6.0+, uses a custom 'fgfm-ca-cert' with 'fgfm-cert-exclusive' enabled and corresponding certificates installed on FortiGates; its effectiveness depends on attackers being unable to obtain a certificate signed by that CA. Older releases must first upgrade to a version supporting these controls. Investigate unexpected device registrations, administrator accounts, configuration changes, and VPN activity; isolate suspected compromised appliances while preserving evidence.
Remediation
Patch, then assume compromise.
Upgrade FortiManager to 7.6.1, 7.4.5, 7.2.8, 7.0.13, 6.4.15, or 6.2.13, or a later fixed release in the corresponding branch. Upgrade affected FortiManager Cloud deployments to 7.4.5, 7.2.8, or 7.0.13 or later; migrate Cloud 6.4 deployments to a fixed release. Apply product-specific guidance to affected FortiAnalyzer deployments. For compromised systems, preserve forensic evidence, deploy a fresh FortiManager VM or reinitialize the hardware, and rediscover managed devices or restore a verified backup predating compromise. Rebuild databases or resynchronize configurations as necessary. Urgently rotate exposed credentials, certificates, private keys, VPN and HA pre-shared keys, authentication-service secrets, and other sensitive secrets held for FortiManager and its managed devices. Review managed-device logs from the earliest identified compromise. Patching alone does not remove established access or invalidate stolen secrets.
Exploits
6 exploits validated by Mallory's analysis.
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.
References
Frequently asked questions
- Is CVE-2024-47575 exploited in the wild?
- Yes. As of Nov 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Oct 23, 2024.
- Is there a public exploit for CVE-2024-47575?
- Yes. Mallory tracks 6 public exploits or proofs of concept for CVE-2024-47575, the earliest disclosed Oct 23, 2024.
- Is there a patch for CVE-2024-47575?
- Upgrade FortiManager to 7.6.1, 7.4.5, 7.2.8, 7.0.13, 6.4.15, or 6.2.13, or a later fixed release in the corresponding branch. Upgrade affected FortiManager Cloud deployments to 7.4.5, 7.2.8, or 7.0.13 or later; migrate Cloud 6.4 deployments to a fixed release.
- What products are affected by CVE-2024-47575?
- Fortinet Fortimanager and Fortinet Fortimanager Cloud.
- How severe is CVE-2024-47575?
- CVE-2024-47575 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 94.8% (100th percentile) as of Nov 16, 2026.
Recent activity
88 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.