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 21 Nov 2025.
FortiwebApplication · Fortinet

CVE-2025-64446

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-14
Fix available
A fix is available. Upgrade to 7.0.12 / 7.2.12 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 relative path traversal vulnerability in Fortinet FortiWeb 8.0.0 through 8.0.1, FortiWeb 7.6.0 through 7.6.4, FortiWeb 7.4.0 through 7.4.9, FortiWeb 7.2.0 through 7.2.11, FortiWeb 7.0.0 through 7.0.11 may allow an attacker to execute administrative commands on the system via crafted HTTP or HTTPS 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

A relative path traversal vulnerability in FortiWeb allows attackers to execute administrative commands via crafted HTTP/HTTPS requests. The vulnerability affects multiple version ranges (7.0.x through 8.0.x) and is exploitable remotely without authentication given the critical CVSS score.

MitigationApply vendor-supplied patches to upgrade FortiWeb to patched versions; as a temporary measure, restrict management interface access to trusted networks only.

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.0.12>= 7.2.0, < 7.2.12>= 7.4.0, < 7.4.10>= 7.6.0, < 7.6.5>= 8.0.0, < 8.0.2

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. Check FortiWeb firmware version
    Log into the FortiWeb CLI and run: `get system status` or check in the web UI under Dashboard > Status. Alternatively, check from FortiGate/FortiManager if centrally managed.
    Affected if The installed version falls within any of these ranges: 7.0.0 to 7.0.11, 7.2.0 to 7.2.11, 7.4.0 to 7.4.9, 7.6.0 to 7.6.4, or 8.0.0 to 8.0.1
  2. Verify administrative interface exposure
    Check if the FortiWeb admin web interface (HTTP/HTTPS port 80/443 or custom admin port) is reachable from untrusted networks. Review firewall policies and network ACLs protecting the management interface.
    Affected if The administrative interface is accessible from the internet or from untrusted internal networks without IP restrictions
  3. Review allowed IP configuration
    In FortiWeb web UI, go to System > Admin > Administrators and check the Trusted Hosts setting for each admin account, or run `show system admin` in CLI to review trusted host definitions.
    Affected if Administrative accounts lack trusted host restrictions (0.0.0.0/0 is configured) or trusted hosts do not cover only your management stations

You are affected if your FortiWeb version is below 7.0.12, 7.2.12, 7.4.10, 7.6.5, or 8.0.2 AND the admin interface is accessible from untrusted networks without IP allowlisting in place.

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.0.12 / 7.2.12 / 7.4.10 or later
Fixed in 7.0.127.2.127.4.10
Interim mitigation

Apply vendor-supplied patches to upgrade FortiWeb to patched versions; as a temporary measure, restrict management interface access to trusted networks only.

Recommended fix High confidence

Upgrade to FortiWeb 7.0.12, 7.2.12, 7.4.10, or 7.6.5 (or later) depending on your current version branch

  1. 1. Identify the currently installed FortiWeb version using the web UI (System > Status) or CLI: 'get system status'
  2. 2. Determine the appropriate upgrade path based on your current version branch (7.0.x -> 7.0.12, 7.2.x -> 7.2.12, 7.4.x -> 7.4.10, or 7.6.x -> 7.6.5)
  3. 3. Download the corresponding firmware upgrade file from Fortinet's support portal (support.fortinet.com) after authenticating
  4. 4. Back up the current FortiWeb configuration via the web UI (System > Maintenance > Backup & Restore) or CLI: 'execute backup full-config'
  5. 5. Upload the firmware file via System > Maintenance > Firmware or via CLI: 'execute restore firmware'
  6. 6. After the device reboots, verify the upgrade was successful: 'get system status' to confirm the new version number
  7. 7. Verify the vulnerability is remediated by confirming the installed version is >= 7.0.12, 7.2.12, 7.4.10, or 7.6.5 respectively
Caveat Review Fortinet's release notes for your target version to check for any configuration or feature changes before upgrading; standard upgrade precautions (backup, test in staging) apply

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

Fix this in Fortiweb Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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