dbcve.org
FortiosOperating system · Fortinet

CVE-2025-25252

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 7.0.17 / 7.2.11 or later.
See remediation →
74/100
Remediation priority · Elevated
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 Insufficient Session Expiration vulnerability [CWE-613] in FortiOS SSL VPN 7.6.0 through 7.6.2, 7.4.0 through 7.4.6, 7.2.0 through 7.2.10, 7.0.0 through 7.0.16, 6.4 all versions may allow a remote attacker (e.g. a former admin whose account was removed and whose session was terminated) in possession of the SAML record of a user session to access or re-open that session via re-use of SAML record.

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

FortiOS SSL VPN fails to properly invalidate SAML session records upon account removal or session termination. An attacker with access to a user's SAML session record can replay it to regain access to the VPN even after their account has been terminated or their session explicitly ended.

MitigationApply Fortinet vendor patches for the affected FortiOS versions. Until patches are applied, monitor for unauthorized session reuse and ensure immediate revocation of all active SAML tokens when terminating user access.

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
FortiosOperating system
Affected:>= 6.4.0, < 7.0.17>= 7.2.0, < 7.2.11>= 7.4.0, < 7.4.7>= 7.6.0, < 7.6.3

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

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 FortiOS version
    Run 'get system status' or 'fortios -v' via CLI to retrieve the installed FortiOS version
    Affected if The version falls within >= 6.4.0 and < 7.0.17, OR >= 7.2.0 and < 7.2.11, OR >= 7.4.0 and < 7.4.7, OR >= 7.6.0 and < 7.6.3
  2. Confirm SSL VPN is configured
    Run 'show vpn ssl settings' or 'get vpn ssl' via CLI to check if SSL VPN is enabled
    Affected if SSL VPN is active and running on the FortiOS device
  3. Verify SAML authentication is in use
    Run 'show user saml' or 'get user saml' via CLI to check for SAML configuration
    Affected if SAML-based authentication is configured for SSL VPN or user access
  4. Review active session records for replay indicators
    Examine session tables using 'diagnose vpn ssl list' or 'get vpn ssl monitor' to inspect active SSL VPN sessions and their session tokens
    Affected if SAML session tokens remain active after account termination or explicit session ending is attempted

The environment is affected if FortiOS runs a version within the listed ranges AND SSL VPN with SAML authentication is enabled, with no external session invalidation mechanism 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.17 / 7.2.11 / 7.4.7 or later
Fixed in 7.0.177.2.117.4.7
Interim mitigation

Apply Fortinet vendor patches for the affected FortiOS versions. Until patches are applied, monitor for unauthorized session reuse and ensure immediate revocation of all active SAML tokens when terminating user access.

Recommended fix High confidence

Upgrade to FortiOS 7.0.17, 7.2.11, 7.4.7, or 7.6.3 (depending on your current major version branch)

  1. 1. Identify the current FortiOS version running on the affected device using 'get system status' or via FortiManager/FortiCloud
  2. 2. Determine the appropriate upgrade path based on current version (7.0.x -> 7.0.17, 7.2.x -> 7.2.11, 7.4.x -> 7.4.7, or 7.6.x -> 7.6.3)
  3. 3. Download the firmware upgrade from Fortinet Customer Support portal or Fortiguard (https://www.fortinet.com/support/firmware)
  4. 4. Review Fortinet release notes for the target version to check for any required pre-upgrade steps
  5. 5. Backup the current FortiOS configuration using 'execute backup full-config'
  6. 6. Upload and install the new firmware image via Web UI (System > Firmware) or CLI: 'execute restore image <tftp/ftp/scpc> <filename>'
  7. 7. After reboot, verify the upgrade was successful with 'get system status' showing the new version
  8. 8. Confirm the SSL VPN functionality is working correctly
Caveat Minor: Review release notes for any behavioral changes between your current version and the target version; standard firmware upgrade best practices apply

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

Fix this in Fortios Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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