CVE-2024-23113: Unauthenticated Remote Code Execution in Fortinet fgfmd
- Vendor
- Fortinet
CVE-2024-23113 is an externally controlled format-string vulnerability in the fgfmd daemon implementing Fortinet's FortiGate-to-FortiManager (FGFM) communications. Specially crafted requests can allow a remote, unauthenticated attacker to execute arbitrary code or commands. Affected versions include FortiOS 7.4.0–7.4.2, 7.2.0–7.2.6, and 7.0.0–7.0.13; FortiProxy 7.4.0–7.4.2, 7.2.0–7.2.8, and 7.0.0–7.0.14; FortiPAM 1.2.0, 1.1.0–1.1.2, and 1.0.0–1.0.3; and FortiSwitchManager 7.2.0–7.2.3 and 7.0.0–7.0.3. The vulnerability has a CVSS v3 score of 9.8 and was added to CISA's Known Exploited Vulnerabilities catalog on October 9, 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 permits unauthenticated remote execution of arbitrary code or commands on an affected appliance. This can compromise appliance confidentiality, integrity, and availability, potentially exposing configuration data and credentials, allowing unauthorized configuration changes, or disrupting network security services. Subsequent persistence and movement into connected networks depend on the compromised appliance's privileges and network access.
Mitigation
If you can’t patch tonight, do this now.
If immediate upgrading is not possible, remove FGFM from the allowaccess setting on every interface. This prevents FortiGate discovery from FortiManager, while FortiGate-initiated connections remain possible. Restrict FGFM exposure to dedicated management networks or explicitly authorized peers across both IPv4 and IPv6, including applicable TCP ports 541 and 542. Local-in policies permitting only trusted source addresses reduce exposure but are not a complete workaround because exploitation remains possible from an allowed address. Disabling SSL-VPN does not address this FGFM vulnerability.
Remediation
Patch, then assume compromise.
Follow Fortinet's supported upgrade path to a fixed release. Upgrade FortiOS to 7.4.3, 7.2.7, or 7.0.14 or later within the corresponding branch; FortiProxy to 7.4.3, 7.2.9, or 7.0.16 or later; and FortiSwitchManager to 7.2.4 or 7.0.4 or later. Migrate affected FortiPAM 1.0, 1.1, and 1.2 installations to a vendor-confirmed fixed release; the vendor remediation table does not specify fixed-version targets for those branches. Prefer currently supported, fully patched releases rather than treating these historical minimum versions as current security baselines.
Exploits
No validated public exploits yet. Hidden: 7 rejected by Mallory's analysis as not a working exploit.
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-23113 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 9, 2024.
- Is there a public exploit for CVE-2024-23113?
- As of Nov 16, 2026, Mallory has found no public exploit for CVE-2024-23113.
- Is there a patch for CVE-2024-23113?
- Follow Fortinet's supported upgrade path to a fixed release. Upgrade FortiOS to 7.4.3, 7.2.7, or 7.0.14 or later within the corresponding branch; FortiProxy to 7.4.3, 7.2.9, or 7.0.16 or later; and FortiSwitchManager to 7.2.4 or 7.0.4 or later.
- What products are affected by CVE-2024-23113?
- Fortinet Fortios, Fortinet Fortipam, Fortinet Fortiproxy, and Fortinet Fortiswitchmanager.
- How severe is CVE-2024-23113?
- CVE-2024-23113 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 61.7% (99th percentile) as of Nov 16, 2026.
Recent activity
32 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.