Threats / NETGEAR / CVE-2016-6277
CVE-2016-6277
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
NETGEAR Multiple Routers vulnerability
NETGEAR routers contain an unauthenticated command injection vulnerability allowing remote code execution through unvalidated form input passed directly to the CLI.
Verdict
Today item — known-exploited.
An unauthenticated remote attacker can inject arbitrary commands via web forms on affected NETGEAR routers, achieving code execution with device privileges. The high EPSS score and active exploitation reflect the severity and accessibility of this attack vector.
CISA KEV Yes · 2022-03-074EPSS 0.99781 (verify live)5CVSS 8.8 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3Exploit Weaponized · public exploit · Metasploit module · nuclei template11
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
1004 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-03-07).
Probability (EPSS)
EPSS 0.99781 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) · Affected: NETGEAR, Multiple Routers. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-352 Cross-Site Request Forgery (CSRF) — weakness family: Web / client.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1909 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module, nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify a NETGEAR router model running vulnerable firmware and access its web interface without credentials.
Business
Network perimeter security is bypassed; the router becomes an entry point for lateral movement.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I craft malicious form input containing shell metacharacters and submit it to an unauthenticated endpoint.
Business
Arbitrary code executes with router privileges, compromising all traffic and connected devices.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish persistent access by modifying router configuration or installing backdoors in firmware.
Business
Long-term network compromise enables data exfiltration, man-in-the-middle attacks, and botnet recruitment.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05