CVE-2025-53870: An improper neutralization of special elements used in an os command ('os command injection') vulnerability...
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.
Security readout for executives and security teams
Plain-English summary
Fortinet's FortiAP and FortiAP-W2 wireless access points contain a flaw that lets a logged-in administrator with high privileges run unauthorized operating system commands through a crafted CLI input. Because attackers must already hold privileged access and be local to the device, business risk is contained but real if admin credentials are ever compromised or misused by insiders.
Executive priority
Schedule as a standard patch cycle item rather than an emergency. The requirement for authenticated, high-privileged, local access keeps external risk low, but wireless infrastructure compromise could pivot into user traffic, so remediate during the next planned wireless maintenance window and tighten admin access controls immediately.
Technical view
An OS command injection weakness (CWE-78) in the FortiAP CLI allows an authenticated, high-privileged user to inject shell metacharacters into a specific command, resulting in arbitrary code execution on the access point. Fortinet's advisory FG-IR-26-133 lists affected branches across FortiAP 6.4 through 7.6.2 and FortiAP-W2 7.0 through 7.4.4. CVSS 3.1 is 6.5 (AV:L/AC:L/PR:H/UI:N/C:H/I:H/A:H) with functional exploit maturity noted in the vector.
Likely exposure
Any organization running vulnerable FortiAP or FortiAP-W2 firmware where administrative CLI access is delegated broadly, shared, or reachable from less-trusted management networks. Exposure grows in multi-tenant, MSP-managed, or campus environments where admin credentials rotate infrequently or are held by third parties.
Exploitation context
Not listed in CISA KEV and no public reports of in-the-wild abuse in the provided sources. The CVSS vector marks exploit code maturity as "Functional" and remediation as "Official Fix," indicating a working technique exists but requires local CLI access and admin-level privileges, which limits opportunistic exploitation.
Researcher notes
CWE-78 in a CLI parser typically points to unsanitized argument handling passed to a shell or exec call. The AV:L, PR:H vector indicates a post-authentication escalation path rather than a remote pre-auth flaw. Watch Fortinet PSIRT FG-IR-26-133 for fixed-version tables and any updates to exploit maturity. No public PoC referenced in the source bundle at time of writing.
Mitigation direction
Review Fortinet advisory FG-IR-26-133 and plan upgrades to fixed FortiAP and FortiAP-W2 builds.
Restrict CLI and management-plane access to a dedicated out-of-band network with allowlisted admin hosts.
Rotate FortiAP admin credentials and enforce unique, per-administrator accounts with MFA on upstream jump hosts.
Audit and reduce the number of accounts holding high-privilege roles on FortiAP devices.
Enable centralized logging of CLI sessions to a SIEM for retrospective review.
Validation and detection
Inventory FortiAP and FortiAP-W2 devices and record firmware versions against the advisory's affected list.
Confirm patched builds are deployed by verifying version output after upgrade windows close.
Verify management interfaces are unreachable from user, guest, and internet segments via network path testing.
Review admin account inventory and last-login records for stale or shared credentials.
Correlate CLI command history and syslog against known-good administrator activity baselines.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-78 · source CWE mapping
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.