dbcve.org
FortiosOperating system · Fortinet

CVE-2025-58325

MEDIUM · 6.7 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 7.0.16 / 7.2.11 or later.
See remediation →
69/100
Remediation priority · Elevated
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 Incorrect Provision of Specified Functionality vulnerability [CWE-684] in FortiOS 7.6.0, 7.4.0 through 7.4.5, 7.2.5 through 7.2.10, 7.0.0 through 7.0.15, 6.4 all versions may allow a local authenticated attacker to execute system commands via crafted 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 · moderate confidence

This is a local privilege escalation vulnerability in FortiOS where an authenticated attacker with standard CLI access can execute arbitrary system commands through specially crafted CLI commands. The vulnerability stems from incorrect functionality provision (CWE-684) that fails to properly restrict command execution permissions.

MitigationApply the appropriate FortiOS patch (upgrade to 7.6.1, 7.4.6, 7.2.11, or 7.0.16 or later versions as available) and review user CLI permission profiles to enforce least-privilege 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.16>= 7.2.0, < 7.2.11>= 7.4.0, < 7.4.6= 7.6.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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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. Identify FortiOS version
    Run the command 'get system status' or 'execute FortiOSVersion' via CLI, or check the FortiManager/FortiCloud dashboard for the FortiOS version installed on the device.
    Affected if The version is 6.4.0 to 7.0.15, 7.2.0 to 7.2.10, 7.4.0 to 7.4.5, or exactly 7.6.0.
  2. Verify CLI access is enabled
    Check if the management interface allows CLI access by reviewing 'config system interface' and confirming the 'set telnet enable' or SSH access is configured for administrative interfaces.
    Affected if CLI access (SSH or console) is permitted on any management interface.
  3. Review CLI permission profiles
    Run 'config system accprofile' and examine the CLI command permissions assigned to user profiles, especially for standard or limited admin accounts.
    Affected if Any admin user has a profile with CLI command execution privileges that exceed the intended restriction.
  4. Check for privileged command execution
    Test whether a standard user with limited CLI profile can execute elevated commands (e.g., 'execute ping', 'execute traceroute', or system-level operations) beyond their assigned profile permissions.
    Affected if A user with a restricted CLI profile can execute commands outside their assigned permissions.

Your environment is affected if the FortiOS version falls within any of the affected ranges AND CLI access is available to authenticated users with standard profiles.

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.16 / 7.2.11 / 7.4.6 or later
Fixed in 7.0.167.2.117.4.6
Interim mitigation

Apply the appropriate FortiOS patch (upgrade to 7.6.1, 7.4.6, 7.2.11, or 7.0.16 or later versions as available) and review user CLI permission profiles to enforce least-privilege access.

Recommended fix Moderate confidence

FortiOS 7.0.16 (for 6.4.x/7.0.x), 7.2.11 (for 7.2.x), 7.4.6 (for 7.4.x), or 7.6.1+ (for 7.6.0)

  1. 1. Identify the current FortiOS version by running: get system status
  2. 2. Determine which version branch your current installation falls into (6.4.x, 7.0.x, 7.2.x, 7.4.x, or 7.6.x)
  3. 3. For 6.4.x branch: upgrade to FortiOS 7.0.16 or later
  4. 4. For 7.0.x branch: upgrade to FortiOS 7.0.16 or later
  5. 5. For 7.2.x branch: upgrade to FortiOS 7.2.11 or later
  6. 6. For 7.4.x branch: upgrade to FortiOS 7.4.6 or later
  7. 7. For 7.6.0 branch: upgrade to FortiOS 7.6.1 or later
  8. 8. Download the upgrade image from Fortinet support portal: https://support.fortinet.com/
Caveat Review Fortinet release notes for migration considerations between major versions; some CLI commands may have changed behavior

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-58325 — 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-58325 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