dbcve.org
FortiwebApplication · Fortinet

CVE-2025-59719

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to after 7.6.4 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 verification of cryptographic signature vulnerability in Fortinet FortiWeb 8.0.0, FortiWeb 7.6.0 through 7.6.4, FortiWeb 7.4.0 through 7.4.9 may allow an unauthenticated attacker to bypass the FortiCloud SSO login authentication via a crafted SAML response message.

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

An improper verification of cryptographic signature vulnerability in FortiWeb's FortiCloud SSO SAML authentication allows unauthenticated attackers to bypass authentication by sending crafted SAML response messages. The flaw enables complete authentication bypass without valid credentials.

MitigationUpgrade FortiWeb to version 8.0.1, 7.6.5, or 7.4.10 or later to patch the signature verification flaw. Review SAML configuration and monitor for unauthorized access attempts.

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.4.0, <= 7.4.9>= 7.6.0, <= 7.6.4= 8.0.0

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. Confirm FortiWeb is installed
    Identify if FortiWeb web application firewall product is running in your environment. This may be a physical appliance, virtual machine, or container instance.
    Affected if FortiWeb is not present in your environment, you are not affected by this vulnerability.
  2. Determine FortiWeb version
    Access FortiWeb via CLI, GUI, or API to retrieve the installed version number. Common methods include the 'get system status' CLI command or checking the dashboard in the web UI.
    Affected if Your version falls within 7.4.0 through 7.4.9, 7.6.0 through 7.6.4, or is exactly 8.0.0. Versions outside these ranges or not running FortiWeb are not affected.
  3. Check if FortiCloud SSO SAML authentication is configured
    Review FortiWeb SAML configuration settings. This is typically found in the FortiWeb administrative interface under User > SSO > SAML, or via CLI commands related to SAML and FortiCloud integration.
    Affected if FortiCloud SSO SAML authentication is not enabled or not configured in your FortiWeb deployment, the specific signature verification flaw may not be exploitable in your environment.

You are affected if FortiWeb is running version 7.4.0-7.4.9, 7.6.0-7.6.4, or 8.0.0 AND FortiCloud SSO SAML authentication is configured and enabled.

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 7.6.4
Interim mitigation

Upgrade FortiWeb to version 8.0.1, 7.6.5, or 7.4.10 or later to patch the signature verification flaw. Review SAML configuration and monitor for unauthorized access attempts.

Recommended fix Moderate confidence

Upgrade to FortiWeb 7.4.10+, 7.6.5+, or 8.0.1+ (or latest stable release within your major version branch)

  1. 1. Identify the current FortiWeb version by running 'get system status' or checking the web UI dashboard.
  2. 2. Based on the affected version range, determine the appropriate upgrade path: For 7.4.x versions, upgrade to 7.4.10 or later; For 7.6.x versions, upgrade to 7.6.5 or later; For 8.0.0, upgrade to 8.0.1 or later.
  3. 3. Download the firmware upgrade from the Fortinet Customer Support portal (support.fortinet.com) or FortiGuard.
  4. 4. Before upgrading, back up the FortiWeb configuration using 'execute backup full-config' or the web UI.
  5. 5. Upload the new firmware via the web UI (System > Firmware) or CLI ('execute firmware upgrade').
  6. 6. After upgrade, verify the fix by confirming the version number and testing SAML SSO login functionality.
  7. 7. Review the FortiWeb release notes for the fixed version to confirm the CVE is addressed.
Caveat Review release notes for your specific version upgrade - some firmware upgrades may require minimum hardware specifications or have specific migration considerations

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
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,320
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,312.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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