dbcve.org
Fortimanager CloudApplication · Fortinet

CVE-2025-68649

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 7.4.8 / 7.6.5 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') vulnerability in Fortinet FortiAnalyzer 7.6.0 through 7.6.4, FortiAnalyzer 7.4.0 through 7.4.7, FortiAnalyzer 7.2 all versions, FortiAnalyzer 7.0 all versions, FortiAnalyzer Cloud 7.6.0 through 7.6.4, FortiAnalyzer Cloud 7.4.0 through 7.4.7, FortiAnalyzer Cloud 7.2 all versions, FortiAnalyzer Cloud 7.0 all versions, FortiManager 7.6.0 through 7.6.4, FortiManager 7.4.0 through 7.4.7, FortiManager 7.2 all versions, FortiManager 7.0 all versions, FortiManager Cloud 7.6.0 through 7.6.4, FortiManager Cloud 7.4.0 through 7.4.7, FortiManager Cloud 7.2 all versions, FortiManager Cloud 7.0 all versions may allow a privileged attacker to delete files from the underlying filesystem via crafted CLI requests.

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

A path traversal vulnerability in FortiAnalyzer and FortiManager allows a privileged attacker to delete files outside the intended restricted directory via crafted CLI requests containing directory traversal sequences (e.g., '../'). The vulnerability stems from improper validation of path inputs in the CLI interface.

MitigationApply Fortinet's patches for the affected versions (7.0.x, 7.2.x, 7.4.x, 7.6.0-7.6.4). In the interim, strictly limit administrative CLI access and monitor for suspicious path-based deletion commands.

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
Fortimanager CloudApplication
Affected:>= 7.0.0, < 7.4.8>= 7.6.0, < 7.6.5
FortimanagerApplication
Affected:>= 7.0.0, < 7.4.8>= 7.6.0, < 7.6.5
Fortianalyzer CloudApplication
Affected:>= 7.0.0, < 7.4.8>= 7.6.0, < 7.6.5
FortianalyzerApplication
Affected:>= 7.0.0, < 7.4.8>= 7.6.0, < 7.6.5

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. Determine FortiManager or FortiAnalyzer version
    Run the command 'get system status' in the CLI or check the web UI dashboard for the firmware version
    Affected if The installed version falls within 7.0.0 to 7.4.7, or 7.6.0 to 7.6.4
  2. Confirm CLI interface accessibility
    Verify that the CLI (via SSH console, serial console, or web UI terminal) is enabled and accessible to privileged users
    Affected if CLI access is permitted for administrative accounts
  3. Review CLI command logs for path traversal attempts
    Examine audit logs in the web UI under Log & Report > Event Log > System Events, or run 'execute log filter' commands, looking for CLI operations that contain '../' sequences in file paths
    Affected if Logs contain CLI delete or file operations with directory traversal sequences like '../' outside the expected directory
  4. Check for unauthorized file deletions outside expected directories
    Compare recent file deletion timestamps in the web UI under File Browser or via 'execute ls' commands against known administrative activities
    Affected if Files were deleted from directories outside the intended restricted directories without legitimate administrative action

You are affected if your FortiManager or FortiAnalyzer version is 7.0.0 through 7.4.7 or 7.6.0 through 7.6.4 and the CLI interface is accessible to privileged users.

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.8 / 7.6.5 or later
Fixed in 7.4.87.6.5
Interim mitigation

Apply Fortinet's patches for the affected versions (7.0.x, 7.2.x, 7.4.x, 7.6.0-7.6.4). In the interim, strictly limit administrative CLI access and monitor for suspicious path-based deletion commands.

Recommended fix High confidence

Upgrade to FortiManager/FortiAnalyzer 7.4.8 or later, or 7.6.5 or later (depending on your current branch). For 7.0.x and 7.2.x branches, upgrade to 7.4.8 or later.

  1. 1. Log into FortiManager or FortiAnalyzer as an administrator with sufficient privileges
  2. 2. Navigate to System > Settings or use the CLI to backup the current configuration
  3. 3. Download the appropriate firmware image from the Fortinet Support Portal (https://support.fortinet.com/) for your product version
  4. 4. For on-premise devices: Go to System > Firmware > Upload Firmware and select the downloaded image
  5. 5. For cloud instances: Use the cloud provider's console or Fortinet cloud management to initiate the firmware upgrade
  6. 6. Wait for the upgrade process to complete and the device to reboot
  7. 7. Verify the device is running the fixed version (7.4.8 or higher for 7.4.x branch, 7.6.5 or higher for 7.6.x branch)
  8. 8. Confirm that the system is functioning normally and review logs for any errors
Caveat Standard firmware upgrade risks apply - ensure configuration backup before upgrading and test in a non-production environment first if possible

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

Fix this in Fortimanager Cloud Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
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,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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