dbcve.org
FortiwebApplication · Fortinet

CVE-2024-55594

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-14
Fix available
A fix is available. Upgrade to 7.4.7 or later.
See remediation →
100/100
Remediation priority · Urgent
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
An improper handling of syntactically invalid structure in Fortinet FortiWeb at least vesrions 7.4.0 through 7.4.6 and 7.2.0 through 7.2.10 and 7.0.0 through 7.0.10 allows attacker to execute unauthorized code or commands via HTTP/S 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 · moderate confidence

FortiWeb WAF fails to properly handle malformed HTTP request structures, allowing attackers to achieve remote code execution through specially crafted HTTP/S requests. This is a critical input validation flaw in the web request parsing layer.

MitigationApply Fortinet's patches for FortiWeb versions 7.4.7, 7.2.11, and 7.0.11 or later. If immediate patching is not feasible, restrict HTTP/S access to trusted sources only using network access controls.

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
FortiwebApplication
Affected:>= 7.0.0, < 7.4.7

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 FortiWeb version
    Run `get system status` or `fnsysctl get system status` from CLI, or check System > Firmware in web UI
    Affected if Version is 7.0.0 through 7.4.6 inclusive (any version >= 7.0.0 and < 7.4.7)
  2. Confirm HTTP/HTTPS management or WAF interface is exposed
    Check interface configuration with `show system interface` and verify HTTP/HTTPS service is enabled on any external-facing interface
    Affected if HTTP or HTTPS service is bound to an interface reachable from untrusted networks (not just localhost/internal)
  3. Verify WAF policy is active
    Run `get waf profile` or check WAF > Web Application Firewall > Profile in web UI to confirm a WAF policy is applied to the protected traffic
    Affected if A WAF policy is currently active and processing incoming HTTP/S requests on the exposed interface
  4. Review logs for malformed request anomalies
    Run `execute log filter category 4` then `execute log display` to check WAF logs for parsing errors, or check Log & Report > Attack Log for suspicious malformed request patterns
    Affected if Logs show unusual parsing errors or patterns consistent with malformed HTTP requests, especially from external sources

You are affected if FortiWeb version is 7.0.0 through 7.4.6 and HTTP/HTTPS management or WAF-protected interfaces are externally accessible.

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 7.4.7 or later
Fixed in 7.4.7
Interim mitigation

Apply Fortinet's patches for FortiWeb versions 7.4.7, 7.2.11, and 7.0.11 or later. If immediate patching is not feasible, restrict HTTP/S access to trusted sources only using network access controls.

Recommended fix High confidence

FortiWeb 7.4.7 or later (7.4.x branch); 7.2.11 or later (7.2.x branch); 7.0.11 or later (7.0.x branch)

  1. 1. Identify the currently installed FortiWeb version by running: get system status
  2. 2. For FortiWeb 7.4.x deployments: Upgrade to version 7.4.7 or later
  3. 3. For FortiWeb 7.2.x deployments: Upgrade to version 7.2.11 or later
  4. 4. For FortiWeb 7.0.x deployments: Upgrade to version 7.0.11 or later
  5. 5. Download the firmware from Fortinet Customer Support portal or FortiGuard: https://www.fortinet.com/support/center/my-account.html#downloads
  6. 6. Before upgrading, backup the current configuration using: execute backup full-config
  7. 7. Upload and install the new firmware via the FortiWeb GUI (System > Firmware) or CLI: execute firmware upgrade
  8. 8. After reboot, verify the upgrade was successful: get system status
Caveat Review Fortinet release notes for 7.4.7/7.2.11/7.0.11 for any configuration or behavioral changes that may require adjustments

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

Fix this in Fortiweb Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-55594 — 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-55594 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