dbcve.org
FortiosOperating system · Fortinet

CVE-2025-61624

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 1.7.1 / 7.0.7 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') [CWE-22] vulnerability in Fortinet FortiOS 7.6.0 through 7.6.4, FortiOS 7.4.0 through 7.4.9, FortiOS 7.2 all versions, FortiOS 7.0 all versions, FortiOS 6.4 all versions, FortiPAM 1.7.0, FortiPAM 1.6 all versions, FortiPAM 1.5 all versions, FortiPAM 1.4 all versions, FortiPAM 1.3 all versions, FortiPAM 1.2 all versions, FortiPAM 1.1 all versions, FortiPAM 1.0 all versions, FortiProxy 7.6.0 through 7.6.4, FortiProxy 7.4.0 through 7.4.11, FortiProxy 7.2 all versions, FortiProxy 7.0 all versions, FortiSwitchManager 7.2.0 through 7.2.7, FortiSwitchManager 7.0.0 through 7.0.6 may allow an authenticated attacker with admin profile and at least read-write permissions to write or delete arbitrary files via specific CLI commands.

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

This is a path traversal vulnerability in Fortinet's CLI that allows authenticated administrators with read-write permissions to write or delete arbitrary files outside intended directories. The vulnerability stems from improper limitation of pathnames to restricted directories in specific CLI commands across FortiOS, FortiPAM, FortiProxy, and FortiSwitchManager products.

MitigationApply available vendor patches for affected FortiOS, FortiPAM, FortiProxy, and FortiSwitchManager versions. Until patched, limit admin profiles to minimum required permissions and monitor CLI command execution for suspicious activity.

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.10>= 7.6.0, < 7.6.5
FortipamOperating system
Affected:>= 1.0.0, < 1.7.1
FortiproxyApplication
Affected:>= 7.0.0, < 7.4.12>= 7.6.0, < 7.6.5
FortiswitchmanagerApplication
Affected:>= 7.0.0, < 7.0.7>= 7.2.0, < 7.2.8

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/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 the Fortinet product
    Determine which Fortinet product is running in your environment: FortiOS (FortiGate), FortiPAM, FortiProxy, or FortiSwitchManager. This can be done via the CLI command 'get system status' or through the web UI dashboard.
    Affected if The product is one of FortiOS, FortiPAM, FortiProxy, or FortiSwitchManager and the version falls within the affected ranges.
  2. Check the installed version
    Run 'get system status' in the CLI to retrieve the firmware version. Compare this version against the affected ranges: FortiOS >= 6.4.0 and < 7.4.10, or >= 7.6.0 and < 7.6.5; FortiPAM >= 1.0.0 and < 1.7.1; FortiProxy >= 7.0.0 and < 7.4.12, or >= 7.6.0 and < 7.6.5; FortiSwitchManager >= 7.0.0 and < 7.0.7, or >= 7.2.0 and < 7.2.8.
    Affected if The installed version falls within any of the affected version ranges listed.
  3. Verify CLI administrator access
    Confirm that administrators have CLI access to the device. This vulnerability is exploitable through the CLI interface, so determine if CLI access is enabled and which administrators can access it.
    Affected if CLI access is available to administrators with read-write permissions.
  4. Review admin profile permissions
    List all administrator accounts and their assigned profiles using 'get system admin' in the CLI. Identify accounts with profiles that grant read-write permissions, as the vulnerability requires this privilege level.
    Affected if Any administrator account has a profile with read-write permissions.
  5. Audit recent CLI command execution
    Review CLI logs and command history for any unusual file operation commands, particularly those involving path traversal patterns such as '../' or accessing directories outside the expected scope. Use 'execute log display' or check the logging infrastructure for CLI audit trails.
    Affected if Suspicious CLI commands involving arbitrary file operations are observed.

Your environment is affected if you are running any of the listed Fortinet products within the specified version ranges and administrators with CLI read-write access exist.

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 1.7.1 / 7.0.7 / 7.2.8 or later
Fixed in 1.7.17.0.77.2.8
Interim mitigation

Apply available vendor patches for affected FortiOS, FortiPAM, FortiProxy, and FortiSwitchManager versions. Until patched, limit admin profiles to minimum required permissions and monitor CLI command execution for suspicious activity.

Recommended fix High confidence

FortiOS: upgrade to 7.4.10 or 7.6.5 | FortiPAM: upgrade to 1.7.1 | FortiProxy: upgrade to 7.4.12 or 7.6.5 | FortiSwitchManager: upgrade to 7.0.7 or 7.2.8

  1. 1. Identify the specific Fortinet product (FortiOS, FortiPAM, FortiProxy, or FortiSwitchManager) and current version running in your environment
  2. 2. Determine the appropriate upgrade path based on your current major version branch (e.g., if on 7.4.x upgrade to 7.4.10, if on 7.6.x upgrade to 7.6.5)
  3. 3. Review the Fortinet release notes for the target fixed version to understand any changes or prerequisites
  4. 4. Download the firmware image from Fortinet support portal (support.fortinet.com) or FortiGuard
  5. 5. Back up the current configuration before proceeding with the upgrade
  6. 6. Upload the firmware via FortiOS CLI using 'execute firmware upload' or through the web UI under System > Firmware
  7. 7. After upgrade, verify the system is functioning normally and confirm the version has been updated
  8. 8. Restrict admin profile assignments - ensure only necessary users have both admin profile AND read-write permissions to limit attack surface
Caveat Standard Fortinet firmware upgrade - review release notes for any configuration changes or deprecated features; backup before upgrade

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

Fix this in Fortios Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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