dbcve.org
FortiosOperating system · Fortinet

CVE-2025-67862

MEDIUM · 6.7 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 7.2.11 / 7.2.15 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 Internal Asset Exposed to Unsafe Debug Access Level or State vulnerability [CWE-1244] vulnerability in Fortinet FortiOS 7.6.0 through 7.6.2, FortiOS 7.4.0 through 7.4.7, FortiOS 7.2.0 through 7.2.10, FortiOS 7.0.0 through 7.0.16, FortiOS 6.4 all versions, FortiProxy 7.6.0 through 7.6.3, FortiProxy 7.4.0 through 7.4.10, FortiProxy 7.2.0 through 7.2.14, FortiProxy 7.0 all versions may allow an authenticated admin to execute lua scripts 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 vulnerability in FortiOS and FortiProxy allows authenticated administrators to execute arbitrary Lua scripts through specially crafted CLI commands, exploiting debug-level functionality that should be restricted. The flaw affects multiple version branches across both product lines and enables privilege escalation through the Lua execution capability.

MitigationRestrict administrative access to trusted users only and update to the fixed versions as specified in Fortinet's security advisory. If immediate patching is not possible, review and limit admin privileges to essential personnel only.

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, <= 6.4.16>= 7.0.0, <= 7.0.16>= 7.2.0, < 7.2.11>= 7.4.0, < 7.4.8>= 7.6.0, < 7.6.3
FortiproxyApplication
Affected:>= 7.0.0, <= 7.0.23>= 7.2.0, < 7.2.15>= 7.4.0, < 7.4.11>= 7.6.0, < 7.6.4

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 the FortiOS or FortiProxy version
    Run the command `get system status` or `diagnose system version` via CLI to retrieve the installed firmware version
    Affected if The version falls within these ranges: FortiOS 6.4.0-6.4.16, 7.0.0-7.0.16, 7.2.0-7.2.10, 7.4.0-7.4.7, 7.6.0-7.6.2 OR FortiProxy 7.0.0-7.0.23, 7.2.0-7.2.14, 7.4.0-7.4.10, 7.6.0-7.6.3
  2. Verify debug interface accessibility
    Check if the debug CLI commands are available by attempting to enter debug mode via `diagnose debug` command, or review the system configuration for debug feature enablement
    Affected if The debug interface is accessible to authenticated administrator accounts without additional restrictions
  3. Review admin CLI command logs for Lua script execution
    Use `execute log filter` to view admin CLI logs, searching for patterns such as `lua`, `luaexec`, or debug-related commands executed outside of normal troubleshooting workflows
    Affected if Logs show execution of debug Lua commands by administrators who should not have elevated script execution privileges
  4. Audit administrator role permissions
    Review the configured administrator profiles and accounts using `get system admin` and `get system admin profile` to identify which admins have debug or privileged execution permissions
    Affected if Multiple administrator accounts exist with permissions to access debug features beyond what their role requires

A system is affected if it runs a FortiOS or FortiProxy version within the affected ranges listed above AND has debug features accessible to authenticated administrators beyond their intended scope.

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.2.11 / 7.2.15 / 7.4.8 or later
Fixed in 7.2.117.2.157.4.8
Interim mitigation

Restrict administrative access to trusted users only and update to the fixed versions as specified in Fortinet's security advisory. If immediate patching is not possible, review and limit admin privileges to essential personnel only.

Recommended fix High confidence

FortiOS: 7.0.17+, 7.2.11+, 7.4.8+, 7.6.3+ (6.4.x users migrate to 7.0+); FortiProxy: 7.0.24+, 7.2.15+, 7.4.11+, 7.6.4+

  1. 1. Identify the currently installed FortiOS or FortiProxy version using 'get system status' CLI command
  2. 2. For FortiOS 6.4.x (6.4.0-6.4.16): Upgrade to FortiOS 7.0.17 or later (7.0.x is the nearest supported branch with fix)
  3. 3. For FortiOS 7.0.x (7.0.0-7.0.16): Upgrade to FortiOS 7.0.17 or later
  4. 4. For FortiOS 7.2.x (7.2.0-7.2.10): Upgrade to FortiOS 7.2.11 or later
  5. 5. For FortiOS 7.4.x (7.4.0-7.4.7): Upgrade to FortiOS 7.4.8 or later
  6. 6. For FortiOS 7.6.x (7.6.0-7.6.2): Upgrade to FortiOS 7.6.3 or later
  7. 7. For FortiProxy 7.0.x (7.0.0-7.0.23): Upgrade to FortiProxy 7.0.24 or later, or migrate to 7.2.15+/7.4.11+/7.6.4+
  8. 8. For FortiProxy 7.2.x (7.2.0-7.2.14): Upgrade to FortiProxy 7.2.15 or later
Caveat Upgrading major versions (e.g., 6.4 to 7.0) may introduce feature changes or require configuration adjustments; review Fortinet upgrade paths and release notes before proceeding

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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