Wap125 FirmwareOperating system · Cisco
CVE-2021-1548
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 · uneditedMultiple vulnerabilities in the web-based management interface of certain Cisco Small Business 100, 300, and 500 Series Wireless Access Points could allow an authenticated, remote attacker to perform command injection attacks against an affected device. These vulnerabilities are due to improper validation of user-supplied input. An attacker could exploit these vulnerabilities by sending crafted HTTP requests to the web-based management interface of an affected system. A successful exploit could allow the attacker to execute arbitrary commands with root privileges on the device. To exploit these vulnerabilities, the attacker must have valid administrative credentials for the device.
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 confidenceCommand injection vulnerability in the web-based management interface of Cisco Small Business 100, 300, and 500 Series Wireless Access Points. Due to improper validation of user-supplied input in HTTP requests, an authenticated attacker with valid admin credentials can execute arbitrary commands with root privileges on affected devices.
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
Wap125 FirmwareOperating system
<= 1.0.3.1
Wap131 FirmwareOperating system
<= 1.0.2.17
Wap150 FirmwareOperating system
<= 1.1.2.4
Wap351 FirmwareOperating system
<= 1.0.2.17
Wap361 FirmwareOperating system
<= 1.1.2.4
Wap581 FirmwareOperating system
<= 1.0.3.1CVSS 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
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the wireless access point modelLocate the model number on the device physical label or check the web-based management interface system information page for the exact model (WAP125, WAP131, WAP150, WAP351, WAP361, or WAP581)Affected if The model is one of: WAP125, WAP131, WAP150, WAP351, WAP361, or WAP581
-
Determine the installed firmware versionLog into the web-based management interface and navigate to the Administration or System Summary page to view the firmware version, or check the device status pageAffected if The firmware version is at or below: 1.0.3.1 for WAP125/WAP581, 1.0.2.17 for WAP131/WAP351, or 1.1.2.4 for WAP150/WAP361
-
Verify if web-based management interface is enabledIn the web interface, go to Access Control or Wireless settings and confirm the HTTP/HTTPS management access is active; alternatively, attempt to reach the device login page on ports 80 or 443 from your workstationAffected if The web-based management interface is accessible and enabled on the device
-
Confirm admin account exists on the deviceIn the web interface, navigate to Administration or User Management to list configured administrator accounts, or check if you can log in with admin credentialsAffected if At least one administrator account is configured and active on the device
You are affected if you have a WAP125, WAP131, WAP150, WAP351, WAP361, or WAP581 device running firmware at or below the specified version limits AND the web-based management interface is accessible with active admin credentials.
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 dataApply Cisco's firmware updates for affected access point models. If no patch is available, restrict web management interface access to trusted networks/VPN, use strong administrative credentials, and consider disabling web-based management if not required.
Fix this in Wap125 Firmware
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1548 — 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-1548 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