dbcve.org
FortiapApplication · Fortinet

CVE-2025-53870

MEDIUM · 6.7 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 7.2.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 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-W2 7.4.0 through 7.4.4, FortiAP-W2 7.2 all versions, FortiAP-W2 7.0 all versions may allow an authenticated attacker to execute unauthorized code or commands via a specifically crafted cli command.

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 Fortinet FortiAP wireless access points allows authenticated attackers to execute arbitrary operating system commands by submitting specially crafted CLI commands. The vulnerability results from improper neutralization of special elements in user input that gets passed to system shell calls.

MitigationApply vendor-supplied patches for affected FortiAP versions; restrict CLI access to trusted administrators only and monitor for suspicious command patterns.

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 W2Application
Affected:>= 7.2.0, < 7.2.6>= 7.4.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 FortiAP model type
    Access the FortiAP management interface or check the physical device label to determine if the unit is a FortiAP or FortiAP W2 variant
    Affected if The device is a FortiAP W2 model (requires different version range check)
  2. Check FortiAP firmware version
    Use the FortiAP CLI command 'get system status' or check via FortiGate controller under Managed FortiAPs to retrieve the current firmware version
    Affected if The installed version falls within: FortiAP >= 6.4.0 and < 7.4.6, or >= 7.6.0 and < 7.6.3; FortiAP W2 >= 7.2.0 and < 7.2.6, or >= 7.4.0 and < 7.4.5
  3. Verify CLI access is enabled
    Check FortiAP configuration for enabled CLI access methods (SSH/Telnet) via FortiGate management interface under FortiAP profile settings or by examining 'fgfm-cli-dev-list' output
    Affected if CLI access (SSH or console) is enabled and reachable from untrusted networks
  4. Review CLI command logs for anomalies
    Examine FortiGate/FortiAP logs for unexpected or suspicious CLI commands, particularly those containing shell metacharacters (;, |, &, $) or unusual command patterns
    Affected if Logs contain CLI commands that are unexpected, particularly those attempting shell command injection patterns

You are affected if your FortiAP or FortiAP W2 device runs a firmware version within the affected ranges AND has CLI access enabled for untrusted 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.2.6 / 7.4.5 / 7.4.6 or later
Fixed in 7.2.67.4.57.4.6
Interim mitigation

Apply vendor-supplied patches for affected FortiAP versions; restrict CLI access to trusted administrators only and monitor for suspicious command patterns.

Recommended fix High confidence

FortiAP: 7.4.6+ or 7.6.3+ | FortiAP-W2: 7.2.6+ or 7.4.5+

  1. 1. Identify the FortiAP or FortiAP-W2 device model and current firmware version via FortiManager or the device CLI (using 'get system status').
  2. 2. Download the appropriate fixed firmware from Fortinet Customer Support portal: https://support.fortinet.com/ (requires active contract).
  3. 3. For FortiAP devices: upgrade to FortiAP 7.4.6 or later, or 7.6.3 or later (depending on your major version branch).
  4. 4. For FortiAP-W2 devices: upgrade to FortiAP-W2 7.2.6 or later, or 7.4.5 or later (depending on your major version branch).
  5. 5. Upload the firmware via FortiGate or FortiManager: go to WiFi Controller > FortiAP > Managed FortiAPs, select the device, and use 'Upgrade' action.
  6. 6. Alternatively, use CLI on the controlling FortiGate: 'execute wireless-controller provision fortiap <serial-number> firmware <image-name>'.
  7. 7. After upgrade, verify the new firmware version with 'get system status' on the FortiAP CLI and confirm the vulnerability is resolved.
Caveat Review Fortinet release notes for upgrade path; firmware upgrades may require controller compatibility and cause brief service interruption during provisioning.

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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