Certain NETGEAR devices are affected by CSRF.
Certain NETGEAR devices are affected by CSRF. This affects CM400 before 2017-01-11, CM600 before 2017-01-11, D1500 before 2017-01-11, D500 before 2017-01-11, DST6501 before 2017-01-11, JNR1010v1 before 2017-01-11, JWNR2000Tv3 before 2017-01-11, JWNR2010v3 before 2017-01-11, PLW1000 before 2017-01-11, PLW1010 before 2017-01-11, WNR500 before 2017-01-11, WNR612v3 before 2017-01-11, N450 before 2017-01-11, and CG3000Dv2 before 2017-01-11.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for help- Published
- Apr 28, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 26th percentile
- CWE
- CWE-352
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
17
Monitor
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| netgear | cm400 firmware | cpe:2.3:o:netgear:cm400_firmware |
| netgear | cm400 | cpe:2.3:h:netgear:cm400 |
| netgear | cm600 firmware | cpe:2.3:o:netgear:cm600_firmware |
| netgear | cm600 | cpe:2.3:h:netgear:cm600 |
| netgear | d1500 firmware | cpe:2.3:o:netgear:d1500_firmware |
| netgear | d1500 | cpe:2.3:h:netgear:d1500 |
| netgear | d500 firmware | cpe:2.3:o:netgear:d500_firmware |
| netgear | d500 | cpe:2.3:h:netgear:d500 |
| netgear | dst6501 firmware | cpe:2.3:o:netgear:dst6501_firmware |
| netgear | dst6501 | cpe:2.3:h:netgear:dst6501 |
| netgear | jnr1010 firmware | cpe:2.3:o:netgear:jnr1010_firmware |
| netgear | jnr1010 | cpe:2.3:h:netgear:jnr1010 |
and 14 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- netgear cm400 firmwarebefore 2017-01-11
- netgear cm600 firmwarebefore 2017-01-11
- netgear d1500 firmwarebefore 1.0.0.20
- netgear d500 firmwarebefore 2017-01-11
- netgear dst6501 firmwarebefore 1.0.0.36
- netgear jnr1010 firmwarebefore 2017-01-11
- netgear jwnr2000t firmwarebefore 2017-01-11
- netgear jwnr2010 firmwarebefore 2017-01-11
- netgear n450 cg3000d firmwarebefore 2017-01-11
- netgear plw1000 firmwarebefore 1.0.0.22
- netgear plw1010 firmwarebefore 2017-01-11
- netgear wnr500 firmwarebefore 2017-01-11
- netgear wnr612 firmwarebefore 2017-01-11
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-352 · Cross-Site Request Forgery (CSRF)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
nvd-primary
Root cause
State-changing requests rely on the session cookie the browser sends automatically; nothing verifies that the request came from the user’s own page.
The bug in code
The whole CWE-352 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use(session({ cookie: { httpOnly: true } }));app.post("/account/address", updateAddress);Fixed
app.use(session({ cookie: { httpOnly: true, sameSite: "lax" } }));app.post("/account/address", csrfProtection, updateAddress);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.