FortiapApplication · Fortinet
CVE-2021-26106
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 · uneditedAn improper neutralization of special elements used in an OS Command vulnerability in FortiAP's console 6.4.1 through 6.4.5 and 6.2.4 through 6.2.5 may allow an authenticated attacker to execute unauthorized commands by running the kdbg CLI command with specifically crafted arguments.
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 confidenceOS command injection vulnerability in FortiAP wireless access points (versions 6.2.4-6.2.5 and 6.4.1-6.4.5) allows authenticated attackers to execute arbitrary commands via the kdbg CLI command by providing specially crafted arguments due to insufficient input sanitization.
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
>= 6.4.1, < 6.4.6
Fortiap SApplication
>= 6.2.4, < 6.2.6
Fortiap W2Application
>= 6.2.4, < 6.2.6CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify FortiAP modelAccess the FortiAP CLI or management interface and run 'get system status' or check the web UI under FortiAP > FortiAP profile to determine the model (FortiAP, FortiAP S, or FortiAP W2)Affected if Model is FortiAP, FortiAP S, or FortiAP W2
-
Check firmware versionRun 'get system status' in the FortiAP CLI or view the firmware version in the web UI under FortiAP > FortiAP Management. Compare against affected ranges: FortiAP 6.4.1-6.4.5, FortiAP S 6.2.4-6.2.5, FortiAP W2 6.2.4-6.2.5Affected if Version falls within 6.4.1 to 6.4.5 for FortiAP, or 6.2.4 to 6.2.5 for FortiAP S/W2
-
Verify CLI access is enabledCheck the FortiGate controller configuration under WiFi Controller > FortiAP Settings to confirm CLI access is permitted for managed FortiAP devicesAffected if CLI access is enabled and the device is managed by a FortiGate controller
-
Check for suspicious kdbg command usageReview FortiAP CLI audit logs or FortiGate logs for any executed 'kdbg' commands. Run ' diagnose wireless-controller + | grep kdbg' on the FortiGate if availableAffected if Any kdbg commands appear in logs, especially with unusual arguments
You are affected if your FortiAP device runs firmware version 6.4.1-6.4.5 (FortiAP), 6.2.4-6.2.5 (FortiAP S), or 6.2.4-6.2.5 (FortiAP W2) and has CLI access enabled.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data6.2.66.4.6
Upgrade FortiAP firmware to version 6.4.6, 7.0.0, or later to resolve the command injection flaw. If immediate patching is not feasible, restrict administrative access to the CLI and monitor for suspicious kdbg command usage.
Fix this in Fortiap
Scoped from the published advisory
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-26106 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-26106 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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