# CVE-2016-6277: NETGEAR Multiple Routers Remote Code Execution

> Remote attackers can execute arbitrary commands on NETGEAR routers via shell metacharacters in the path info to cgi-bin.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 7 Mar 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Dec 2016
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-pxpc-qfm6-wwp4

## What is CVE-2016-6277?

CVE-2016-6277 is a high-severity command injection vulnerability in Netgear D6220 Firmware, published on 14 Dec 2016. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

NETGEAR R6250 before 1.0.4.6.Beta, R6400 before 1.0.1.18.Beta, R6700 before 1.0.1.14.Beta, R6900, R7000 before 1.0.7.6.Beta, R7100LG before 1.0.0.28.Beta, R7300DST before 1.0.0.46.Beta, R7900 before 1.0.1.8.Beta, R8000 before 1.0.3.26.Beta, D6220, D6400, D7000, and possibly other routers allow remote attackers to execute arbitrary commands via shell metacharacters in the path info to cgi-bin/.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2016-6277?

It affects 11 products.


Products: Netgear D6220 Firmware, Netgear D6400 Firmware, Netgear R6250 Firmware, Netgear R6400 Firmware, Netgear R6700 Firmware, Netgear R6900 Firmware, Netgear R7000 Firmware, Netgear R7100lg Firmware, Netgear R7300dst Firmware, Netgear R7900 Firmware, Netgear R8000 Firmware.

## How do I fix CVE-2016-6277?

No fix has been published for CVE-2016-6277 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 7 Sep 2022.

## Is CVE-2016-6277 being exploited?

Yes. Attackers have exploited CVE-2016-6277 in the wild since at least 7 Mar 2022.

Public exploit code:

- Netgear R7000 and R6400 cgi-bin Command Injection (metasploit)
- Netgear R7000 - Command Injection (exploitdb)
- Netgear R7000 / R6400 - 'cgi-bin' Command Injection (Metasploit) (exploitdb)
- Netgear R7000 / R6400 - 'cgi-bin' Command Injection (Metasploit) (exploitdb)
- NETGEAR Routers - Remote Code Execution (nuclei): http/cves/2016/CVE-2016-6277.yaml

## Other vulnerabilities in Netgear D6220 Firmware

- [CVE-2021-45527](https://insights.sbomify.com/CVE-2021-45527/): Memory corruption in n/a (critical 9.6)
- [CVE-2021-45610](https://insights.sbomify.com/CVE-2021-45610/): Memory corruption in n/a (critical 9.6)
- [CVE-2021-45638](https://insights.sbomify.com/CVE-2021-45638/): Memory corruption in n/a (critical 9.6)
- [CVE-2021-34982](https://insights.sbomify.com/CVE-2021-34982/): NETGEAR Multiple Routers httpd Stack-based Buffer Overflow Remote Code Execution Vulnerability (high 8.8)
- [CVE-2023-33533](https://insights.sbomify.com/CVE-2023-33533/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-6277 and fix it if it is affected.

What it is: CVE-2016-6277 is a high-severity command injection vulnerability in Netgear D6220 Firmware, published on 14 Dec 2016. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2016-6277 in the wild since at least 7 Mar 2022.

Affected product: Netgear D6220 Firmware. 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-2016-6277/ (Markdown: https://insights.sbomify.com/CVE-2016-6277/index.md)
```

## Sources

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

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