dbcve.org
FortiwebApplication · Fortinet

CVE-2025-64447

HIGH · 8.1 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to after 8.0.1 or later.
See remediation →
90/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
A reliance on cookies without validation and integrity checking vulnerability in Fortinet FortiWeb 8.0.0 through 8.0.1, FortiWeb 7.6.0 through 7.6.5, FortiWeb 7.4.0 through 7.4.10, FortiWeb 7.2.0 through 7.2.11, FortiWeb 7.0.0 through 7.0.11 may allow an unauthenticated attacker to execute arbitrary operations on the system via crafted HTTP or HTTPS request via forged cookies, requiring prior knowledge of the FortiWeb serial number.

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

FortiWeb fails to validate or verify integrity of cookies, allowing unauthenticated attackers to craft malicious cookies and execute arbitrary operations. Exploitation requires prior knowledge of the device serial number, which partially constrains the attack surface.

MitigationApply vendor patches when available. Restrict management interface access to trusted networks, and monitor for anomalous requests using forged cookie values.

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.11>= 7.2.0, <= 7.2.11>= 7.4.0, <= 7.4.10>= 7.6.0, <= 7.6.5>= 8.0.0, <= 8.0.1

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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 installation
    Run the command 'get system status' or 'diagnose system version' via FortiWeb CLI to confirm the product is FortiWeb and note the exact firmware version
    Affected if The product is FortiWeb and the version falls within these ranges: 7.0.0-7.0.11, 7.2.0-7.2.11, 7.4.0-7.4.10, 7.6.0-7.6.5, or 8.0.0-8.0.1
  2. Verify management interface exposure
    Review network configuration via 'show system interface' or check firewall policies to determine if the FortiWeb management interface (port 443/8443) is accessible from untrusted networks
    Affected if The management interface is exposed to the internet or untrusted networks, allowing unauthenticated attackers to reach it
  3. Check for device serial number exposure
    Review whether the device serial number is disclosed in publicly accessible pages, API responses, or is discoverable through reconnaissance
    Affected if The serial number can be obtained through unauthenticated means, satisfying the prior knowledge requirement for exploitation
  4. Inspect logs for anomalous cookie patterns
    Review access logs and security logs for requests containing unusual or unexpected cookie values, using commands like 'execute log filter' and 'execute log display' to search for cookie-related entries
    Affected if Logs show cookie values that appear tampered with, malformed, or contain unexpected content that does not match expected FortiWeb cookie structures

You are affected if FortiWeb is running a version within the ranges 7.0.0-7.0.11, 7.2.0-7.2.11, 7.4.0-7.4.10, 7.6.0-7.6.5, or 8.0.0-8.0.1 AND the management interface is accessible to unauthenticated attackers who could obtain the device serial number.

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 a release after 8.0.1
Interim mitigation

Apply vendor patches when available. Restrict management interface access to trusted networks, and monitor for anomalous requests using forged cookie values.

Recommended fix High confidence

FortiWeb 7.0.12+, 7.2.12+, 7.4.11+, or 7.6.6+ (depending on your current branch)

  1. 1. Identify the current FortiWeb version by navigating to System > Status in the FortiWeb GUI or running 'get system status' in the CLI.
  2. 2. Determine which version branch your current installation belongs to (7.0.x, 7.2.x, 7.4.x, or 7.6.x).
  3. 3. For FortiWeb 7.0.x deployments: upgrade to version 7.0.12 or later.
  4. 4. For FortiWeb 7.2.x deployments: upgrade to version 7.2.12 or later.
  5. 5. For FortiWeb 7.4.x deployments: upgrade to version 7.4.11 or later.
  6. 6. For FortiWeb 7.6.x deployments: upgrade to version 7.6.6 or later.
  7. 7. Download the appropriate firmware from Fortinet's support portal (support.fortinet.com) after logging in with valid entitlements.
  8. 8. Upload the firmware through FortiWeb GUI via System > Maintenance > Firmware > Upload, or via CLI using 'execute firmware upload' command.
Caveat Review FortiWeb release notes for your target version to check for configuration or behavioral changes between your current version and the upgrade version; always test in a staging environment before production deployment

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

Fix this in Fortiweb Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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