dbcve.org
FortiosOperating system · Fortinet

CVE-2025-62631

MEDIUM · 5.6 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 7.4.1 or later.
See remediation →
65/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] vulnerability in Fortinet FortiOS 7.4.0, FortiOS 7.2 all versions, FortiOS 7.0 all versions, FortiOS 6.4 all versions allows attacker to maintain access to network resources via an active SSLVPN session not terminated after a user's password change under particular conditions outside of the attacker's control

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

This is a session management vulnerability (CWE-613) in FortiOS where SSLVPN sessions remain active and valid after a user's password has been changed. An attacker who previously obtained valid session credentials can continue accessing network resources through the persistent session even after the legitimate user's password has been updated, unless specific conditions (likely session termination policies or re-authentication triggers) are met.

MitigationApply the Fortinet patch when available and consider manually terminating active SSLVPN sessions or enforcing re-authentication policies when user password changes occur as an interim control.

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.4.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
Low
Integrity
Low
Availability
Low

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

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 FortiOS version
    Run `get system status` or `get system info` via FortiOS CLI and locate the Firmware/Version field
    Affected if Version is >= 6.4.0 and < 7.4.1
  2. Verify SSLVPN is configured
    Run `get vpn ssl settings` via FortiOS CLI and check if SSLVPN is enabled (look for 'set status enable' or similar)
    Affected if SSLVPN is enabled and the FortiOS version falls within the affected range
  3. Review active SSLVPN sessions
    Run `get vpn ssl monitor` via FortiOS CLI to list currently active SSLVPN sessions
    Affected if There are active sessions and the FortiOS version is in the affected range, as these sessions could remain valid after a password change

You are affected if your FortiOS version is >= 6.4.0 and < 7.4.1 and you have SSLVPN enabled, as password changes will not automatically terminate existing SSLVPN sessions.

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.1 or later
Fixed in 7.4.1
Interim mitigation

Apply the Fortinet patch when available and consider manually terminating active SSLVPN sessions or enforcing re-authentication policies when user password changes occur as an interim control.

Recommended fix High confidence

FortiOS 7.4.1 or later (7.4.x branch recommended)

  1. 1. Back up the current FortiOS configuration to ensure a rollback point is available
  2. 2. Download FortiOS 7.4.1 or later from the Fortinet Customer Support Portal
  3. 3. Upload the firmware image to the FortiGate device via the web UI or CLI
  4. 4. Initiate the firmware upgrade and allow the device to reboot
  5. 5. After reboot, verify the SSLVPN session terminates properly after a user password change by testing the scenario
  6. 6. Confirm the new firmware version is running with 'get system status' CLI command
Caveat Major version upgrades may introduce configuration or feature changes; review Fortinet release notes and test in a lab environment before production deployment

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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