# CVE-2023-31741: Command injection in n/a

> An attacker with web management access can inject commands into specific HTTP parameters to gain shell privileges on the router.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 May 2023
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-vwwm-g3pw-3q86

## What is CVE-2023-31741?

CVE-2023-31741 is a high-severity command injection vulnerability in n/a, published on 23 May 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

There is a command injection vulnerability in the Linksys E2000 router with firmware version 1.0.06. If an attacker gains web management privileges, they can inject commands into the post request parameters wl_ssid, wl_ant, wl_rate, WL_atten_ctl, ttcp_num, ttcp_size in the httpd s Start_EPI() function, thereby gaining shell privileges.

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

## Which versions are affected by CVE-2023-31741?

It affects 1 product.


Products: Linksys E2000 Firmware.

## How do I fix CVE-2023-31741?

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

## Is CVE-2023-31741 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-31741 exists.

## Other vulnerabilities in n/a

- [CVE-2024-27497](https://insights.sbomify.com/CVE-2024-27497/): Auth bypass in n/a (high 8.8)
- [CVE-2023-31740](https://insights.sbomify.com/CVE-2023-31740/): Command injection in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-31741 and fix it if it is affected.

What it is: CVE-2023-31741 is a high-severity command injection vulnerability in n/a, published on 23 May 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-31741 exists.

Affected product: n/a. 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-2023-31741/ (Markdown: https://insights.sbomify.com/CVE-2023-31741/index.md)
```

## Sources

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

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