dbcve.org
FortiapApplication · Fortinet

CVE-2025-53680

MEDIUM · 6.7 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 7.0.6 / 7.4.5 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 improper neutralization of special elements used in an OS command ("OS Command Injection") vulnerability [CWE-78] vulnerability in Fortinet FortiAP 7.6.0 through 7.6.2, FortiAP 7.4.0 through 7.4.5, FortiAP 7.2 all versions, FortiAP 7.0 all versions, FortiAP 6.4 all versions, FortiAP-U 7.0.0 through 7.0.5, FortiAP-U 6.2 all versions, FortiAP-W2 7.4.0 through 7.4.4, FortiAP-W2 7.2 all versions, FortiAP-W2 7.0 all versions allows an authenticated privileged attacker to execute unauthorized code or commands 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

OS Command Injection vulnerability in FortiAP CLI allows authenticated privileged attackers to execute arbitrary OS commands via crafted CLI requests. The vulnerability affects multiple FortiAP product lines across versions 6.4 through 7.6.

MitigationApply vendor-provided patches to upgrade to fixed FortiAP versions. Restrict CLI access to only trusted, privileged users and minimize the attack surface by isolating management interfaces.

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
FortiapApplication
Affected:>= 6.4.0, < 7.4.6>= 7.6.0, < 7.6.3
Fortiap UApplication
Affected:>= 7.0.0, < 7.0.6
Fortiap W2Application
Affected:>= 7.2.0, < 7.4.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
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 FortiAP device model
    Run `get system status` in the FortiAP CLI or check the FortiAP dashboard in FortiGate. Look for the model name (FortiAP, FortiAP U, or FortiAP W2).
    Affected if The device is a FortiAP, FortiAP U, or FortiAP W2 model.
  2. Determine the installed firmware version
    Run `get system status` in the FortiAP CLI or check the FortiGate managed AP firmware version. Note the full version number (for example: 7.4.5 or 7.6.2).
    Affected if A version number is displayed in the output.
  3. Compare version against affected ranges
    Match your identified model and version against these ranges: FortiAP: >= 6.4.0 and < 7.4.6, or >= 7.6.0 and < 7.6.3; FortiAP U: >= 7.0.0 and < 7.0.6; FortiAP W2: >= 7.2.0 and < 7.4.5.
    Affected if Your installed version falls within any of these vulnerable ranges.
  4. Verify CLI access is enabled
    Check FortiAP management settings in FortiGate under WiFi Controller > AP Manager > Managed APs. Confirm CLI access (SSH/telnet to AP) is permitted. Alternatively, run `get system interface` on the FortiAP to list accessible interfaces.
    Affected if CLI access interface (SSH/telnet) is enabled and reachable.
  5. Review privileged CLI user accounts
    In FortiGate, check managed AP administrative users under WiFi Controller > AP Manager > Managed APs > CLI Settings, or query local users on the FortiAP with `get admin user`. Identify accounts with privileged (read-write) access.
    Affected if One or more privileged administrative accounts exist with access to the CLI.

You are affected if your FortiAP model runs a firmware version within the listed vulnerable ranges AND CLI access is enabled for privileged authenticated 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.0.6 / 7.4.5 / 7.4.6 or later
Fixed in 7.0.67.4.57.4.6
Interim mitigation

Apply vendor-provided patches to upgrade to fixed FortiAP versions. Restrict CLI access to only trusted, privileged users and minimize the attack surface by isolating management interfaces.

Recommended fix High confidence

FortiAP: 7.4.6 or 7.6.3 | FortiAP-U: 7.0.6 | FortiAP-W2: 7.4.5

  1. 1. Identify the FortiAP device model (FortiAP, FortiAP-U, or FortiAP-W2) and current firmware version using the FortiOS GUI or CLI: `get system status`
  2. 2. For FortiAP devices: Upgrade to firmware version 7.4.6 or later (if running 7.4.x), or to 7.6.3 or later (if running 7.6.x)
  3. 3. For FortiAP-U devices: Upgrade to firmware version 7.0.6 or later
  4. 4. For FortiAP-W2 devices: Upgrade to firmware version 7.4.5 or later
  5. 5. Download the appropriate firmware from the Fortinet Customer Support portal: https://support.fortinet.com/
  6. 6. Upload the firmware through FortiOS GUI (System > Firmware) or CLI: `execute firmware upgrade <image>`
  7. 7. After upgrade, verify the new firmware version is installed and confirm the vulnerability is resolved
Caveat Review FortiOS release notes for any configuration or feature changes between versions before upgrading

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

Fix this in Fortiap 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-53680 — 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-53680 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