dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 13 Nov 2024.
FortimanagerApplication · Fortinet

CVE-2024-47575

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-23
Fix available
A fix is available. Upgrade to 6.2.13 / 6.4.15 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click

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 · unedited
A missing authentication for critical function in FortiManager 7.6.0, FortiManager 7.4.0 through 7.4.4, FortiManager 7.2.0 through 7.2.7, FortiManager 7.0.0 through 7.0.12, FortiManager 6.4.0 through 6.4.14, FortiManager 6.2.0 through 6.2.12, Fortinet FortiManager Cloud 7.4.1 through 7.4.4, FortiManager Cloud 7.2.1 through 7.2.7, FortiManager Cloud 7.0.1 through 7.0.12, FortiManager Cloud 6.4.1 through 6.4.7 allows attacker to execute arbitrary code or commands via specially crafted 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 confidence

This is a critical pre-authentication remote code execution vulnerability in FortiManager and FortiManager Cloud. The flaw allows unauthenticated attackers to execute arbitrary code or commands on affected systems by sending specially crafted requests to the FortiManager interface, due to missing authentication checks on a critical function.

MitigationImmediately apply the vendor-supplied patches for FortiManager 7.0, 7.2, 7.4, 7.6 and corresponding Cloud versions. As an interim measure, restrict network access to FortiManager management interfaces to trusted IPs only or place behind a VPN until patching is completed.

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
FortimanagerApplication
Affected:>= 6.2.0, < 6.2.13>= 6.4.0, < 6.4.15>= 7.0.0, < 7.0.13>= 7.2.0, < 7.2.8>= 7.4.0, < 7.4.5= 7.6.0
Fortimanager CloudApplication
Affected:>= 6.4.1, <= 6.4.7>= 7.0.1, < 7.0.13>= 7.2.1, < 7.2.8>= 7.4.1, < 7.4.5

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify FortiManager product type
    Determine if the installed FortiManager is the on-premise version (FortiManager) or the cloud-hosted version (FortiManager Cloud). Check product documentation or the system dashboard for the product name.
    Affected if The product is FortiManager or FortiManager Cloud and the version falls within the affected ranges listed in the CVE.
  2. Check installed FortiManager version
    Access the FortiManager system dashboard or use the 'get system status' CLI command to retrieve the current firmware version. Compare this version against the affected ranges: FortiManager >= 6.2.0 < 6.2.13, >= 6.4.0 < 6.4.15, >= 7.0.0 < 7.0.13, >= 7.2.0 < 7.2.8, >= 7.4.0 < 7.4.5, or = 7.6.0. For FortiManager Cloud: >= 6.4.1 <= 6.4.7, >= 7.0.1 < 7.0.13, >= 7.2.1 < 7.2.8, or >= 7.4.1 < 7.4.5.
    Affected if The installed version matches any of the affected version ranges for the respective product.
  3. Verify management interface exposure
    Review network configuration to determine if the FortiManager management interface (typically ports HTTP/HTTPS 80/443) is accessible from untrusted networks or the public internet. Check firewall rules and interface bindings.
    Affected if The management interface is exposed to untrusted networks or the internet, enabling the unauthenticated attacker to send the specially crafted HTTP requests.
  4. Review for indicators of compromise
    Check FortiManager logs, especially authentication logs and audit logs for unexpected commands, unfamiliar administrator accounts, or command injection patterns. Look for anomalous HTTP requests to critical functions.
    Affected if Unexplained commands, unknown administrator accounts, or suspicious log entries indicate potential exploitation.

You are affected if your FortiManager or FortiManager Cloud version falls within the listed affected ranges AND the management interface is network-accessible to untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.2.13 / 6.4.15 / 7.0.13 or later
Fixed in 6.2.136.4.157.0.13
Interim mitigation

Immediately apply the vendor-supplied patches for FortiManager 7.0, 7.2, 7.4, 7.6 and corresponding Cloud versions. As an interim measure, restrict network access to FortiManager management interfaces to trusted IPs only or place behind a VPN until patching is completed.

Recommended fix High confidence

FortiManager: 6.2.13+, 6.4.15+, 7.0.13+, 7.2.8+ | FortiManager Cloud: 6.4.15+, 7.0.13+, 7.2.8+, 7.4.5+

  1. 1. Identify the current FortiManager version by running `get system status` or checking the administration GUI dashboard.
  2. 2. For FortiManager instances: If running 6.2.x, upgrade to 6.2.13 or later. If running 6.4.x, upgrade to 6.4.15 or later. If running 7.0.x, upgrade to 7.0.13 or later. If running 7.2.x, upgrade to 7.2.8 or later.
  3. 3. For FortiManager Cloud instances: If running 6.4.x, upgrade to 6.4.15 or later. If running 7.0.x, upgrade to 7.0.13 or later. If running 7.2.x, upgrade to 7.2.8 or later. If running 7.4.x, upgrade to 7.4.5 or later.
  4. 4. Download the firmware upgrade from the Fortinet Customer Support portal or FortiManager Cloud console.
  5. 5. Back up the FortiManager configuration before applying the upgrade.
  6. 6. Apply the firmware upgrade via the web GUI (System > Firmware) or CLI (`execute system firmware-upgrade`).
  7. 7. Verify the upgrade was successful by checking the system status and ensuring the new version is running.
  8. 8. After upgrade, validate that critical functions still work correctly and monitor for any anomalies.
Caveat Upgrading firmware may cause temporary service disruption; ensure maintenance window and test in staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fortimanager Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47575 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-47575 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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