# CVE-2021-1551: Cisco Small Business 100, 300, and 500 Series Wireless Access Points Command Injection Vulnerabilities

> Authenticated attackers can execute arbitrary commands with root privileges on Cisco Small Business Wireless Access Points via crafted HTTP requests.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 May 2021
- **Updated:** 8 Nov 2024
- **Also known as:** GHSA-v7g5-xxrc-m7qm

## What is CVE-2021-1551?

CVE-2021-1551 is a medium-severity command injection vulnerability in Cisco Business Wireless Access Point Software, published on 22 May 2021. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Multiple 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.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2021-1551?

It affects 6 products.


Products: Cisco Wap125 Firmware, Cisco Wap131 Firmware, Cisco Wap150 Firmware, Cisco Wap351 Firmware, Cisco Wap361 Firmware, Cisco Wap581 Firmware.

## How do I fix CVE-2021-1551?

No fix has been published for CVE-2021-1551 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-1551 being exploited?

There is no known exploitation of CVE-2021-1551 in the wild and no public exploit code.

## Other vulnerabilities in Cisco Business Wireless Access Point Software

- [CVE-2021-1400](https://insights.sbomify.com/CVE-2021-1400/): Cisco Small Business 100, 300, and 500 Series Wireless Access Points Vulnerabilities (high 8.8)
- [CVE-2021-1401](https://insights.sbomify.com/CVE-2021-1401/): Cisco Small Business 100, 300, and 500 Series Wireless Access Points Vulnerabilities (high 8.8)
- [CVE-2021-1547](https://insights.sbomify.com/CVE-2021-1547/): Cisco Small Business 100, 300, and 500 Series Wireless Access Points Command Injection Vulnerabilities (medium 4.7)
- [CVE-2021-1548](https://insights.sbomify.com/CVE-2021-1548/): Cisco Small Business 100, 300, and 500 Series Wireless Access Points Command Injection Vulnerabilities (medium 4.7)
- [CVE-2021-1549](https://insights.sbomify.com/CVE-2021-1549/): Cisco Small Business 100, 300, and 500 Series Wireless Access Points Command Injection Vulnerabilities (medium 4.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-1551 and fix it if it is affected.

What it is: CVE-2021-1551 is a medium-severity command injection vulnerability in Cisco Business Wireless Access Point Software, published on 22 May 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-1551 in the wild and no public exploit code.

Affected product: Cisco Business Wireless Access Point Software. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-1551/ (Markdown: https://insights.sbomify.com/CVE-2021-1551/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-1551
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-1551
- OSV: https://osv.dev/vulnerability/CVE-2021-1551

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-1551/
Summaries are generated and may contain mistakes; the official description above is the record.