Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2024-47575: FortiJump

Published Oct 23, 2024 · Updated 1 day ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days9 mentions · peak 3 in a dayToday
CVSS9.8Critical · v3.1
EPSS94.8%100th percentile
CISA KEVYesAdded Oct 23, 2024
In the wildActivePer CISA KEV
Vendor
Fortinet
IdentifiersCVE-2024-47575CWE-306 · Missing Authentication for…

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.

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 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.

Public exploits

Exploits

6 exploits validated by Mallory's analysis.

View more in app →
fortimanager_rce_cve_2024_47575.rbThis repository contains a single Metasploit module (Ruby) that exploits CVE-2024-47575, a critical unauthenticated remote code execution vulnerability in Fortinet FortiManager and FortiManager Cloud devices. The exploit targets the FGFM service, typically running on TCP port 541 with SSL enabled. The module leverages a missing authentication check, allowing an attacker with a valid Fortinet-signed client certificate (provided by default in the module) to execute arbitrary commands as root on the target system. The module supports user-supplied certificates and allows customization of the serial number and platform if needed. The exploit is operational and provides root-level command execution on a wide range of FortiManager and FortiManager Cloud versions. The code is well-structured, with clear options for certificate/key paths and serial/platform overrides, and includes a check method to verify if the target is a FortiManager device by inspecting its SSL certificate. No hardcoded IPs or domains are present, but the default port (541) and writable directory (/tmp) are fingerprintable endpoints.Disclosed Oct 23, 2024 · Framework: metasploit · ruby · networkWeaponizedFortijump-Exploit-CVE-2024-47575This repository contains a functional exploit for CVE-2024-47575, an unauthenticated remote code execution vulnerability in Fortinet FortiManager and FortiManager Cloud. The main exploit script (CVE-2024-47575.py) is written in Python and leverages a custom SSL connection (using provided certificate and key files) to communicate with the target's management port (TCP 541). The script supports two modes: 'check' (to test for vulnerability) and 'exploit' (to gain code execution). In exploit mode, it sends a crafted payload that causes the target to execute a bash reverse shell, connecting back to the attacker's specified IP and port. The repository also includes a README with usage instructions and a list of affected product versions, as well as the necessary certificate and key files for SSL communication. The exploit is operational and provides a working reverse shell if the target is vulnerable and accessible.watchtowrlabs · Disclosed Nov 7, 2024 · python · networkOperationalexploit-cve-2024-47575This repository contains a Python exploit for CVE-2024-47575, a critical unauthenticated remote code execution vulnerability in Fortinet FortiManager and FortiManager Cloud. The main exploit script, CVE-2024-47575.py, connects to the target's management interface on TCP port 541 using a provided client certificate and key (w00t_cert.bin and w00t_key.bin). It supports two modes: 'check' (to test for vulnerability) and 'exploit' (to gain a reverse shell). In exploit mode, it sends a crafted payload that causes the target to execute a shell command, opening a reverse shell to the attacker's specified host and port. The README provides usage instructions and lists affected product versions. The repository is operational, providing a working exploit with a hardcoded payload, and is not part of a larger framework.SkyGodling · Disclosed Nov 15, 2024 · python · networkOperationalcve-2024-47575-expThis repository provides a proof-of-concept exploit for CVE-2024-47575, a critical unauthenticated remote code execution vulnerability in Fortinet FortiManager and FortiManager Cloud. The main exploit script, 'CVE-2024-47575-poc.py', is a Python tool that connects to the target's TCP port 541 using a custom SSL context with provided certificate and key files. It crafts and sends a series of protocol-specific requests to the fgfmsd daemon, exploiting the lack of authentication to first check for vulnerability and then, if exploitable, to send a payload that executes a reverse shell command. The attacker can specify their own host and port for the reverse shell. The repository includes the necessary certificate and key files, a README in Chinese explaining the vulnerability and its impact, and standard licensing and gitignore files. The exploit is operational and demonstrates full remote code execution capability, requiring only network access to the target and the included certificate/key files.XiaomingX · Disclosed Nov 22, 2024 · python · networkOperationalCVE-2024-47575-POCThis repository is a proof-of-concept exploit for CVE-2024-47575 targeting Fortinet FortiManager. The main code is in 'src/exploit.py', a Python script that connects to a target FortiManager device over SSL (TCP port 541) using a client certificate and key (w00t_cert.bin, w00t_key.bin). The script supports two modes: 'check' (to test for vulnerability) and 'exploit' (to gain a reverse shell). It crafts and sends a series of protocol-specific requests to the target, leveraging the vulnerability to execute a bash reverse shell payload. The exploit requires the attacker to specify their own IP and port for the reverse shell connection. The repository also includes a minimal README and a .gitignore; all exploit logic resides in the Python script.revanslbw · Disclosed Jan 5, 2025 · python · networkOperationalCVE-2024-47575This repository contains two files: 'c.py' and 'start.sh'. The 'c.py' file contains an obfuscated Python payload, encoded with base64 and compressed with zlib. The 'start.sh' script installs the 'requests' library, writes a temporary Python script to '/tmp/1.py' that decodes and executes the obfuscated payload, and then runs this script in the background. The actual functionality of the payload is hidden due to the obfuscation, but the structure suggests it is designed to execute arbitrary or malicious code on the host system. There are no explicit network endpoints or CVE targets visible in the unobfuscated code, but the use of obfuscation and temporary file execution is typical of malware or post-exploitation tools. The repository is not part of a known exploit framework and appears to be a standalone, potentially malicious script.AnnnNix · Disclosed Jul 19, 2025 · python · bash · localPoC
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
FortinetFortimanageroperating_system
FortinetFortimanager Cloudapplication
FAQ

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.
Activity feed

Recent activity

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

View more in app →
+40 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 evidence20Every report linking this CVE to a named adversary.
Associated malware6Malware families linked to this CVE, with evidence and IOCs.
Detection signatures6YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity38Community discussion across Reddit, Mastodon, and other social sources.