Certain NETGEAR devices are affected by CSRF.
Certain NETGEAR devices are affected by CSRF. This affects D6200 before 1.1.00.24, D7000 before 1.0.1.52, JNR1010v2 before 1.1.0.44, JWNR2010v5 before 1.1.0.44, JR6150 before 1.0.1.12, PR2000 before 1.0.0.20, R6020 before 1.0.0.26, R6050 before 1.0.1.12, R6080 before 1.0.0.26, R6120 before 1.0.0.36, R6220 before 1.1.0.60, R6700v2 before 1.2.0.12, R6800 before 1.2.0.12, R6900v2 before 1.2.0.12, WNDR3700v5 before 1.1.0.50, WNR1000v4 before 1.1.0.44, WNR2020 before 1.1.0.44, and WNR2050 before 1.1.0.44.
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 22, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.5% · 39th 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
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CNA vs NVD score
- NVD
- 8.8
- CNA · mitre
- 8.8
- agree
CVSS:3.0/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:R
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| netgear | d6200 firmware | cpe:2.3:o:netgear:d6200_firmware |
| netgear | d6200 | cpe:2.3:h:netgear:d6200 |
| netgear | d7000 firmware | cpe:2.3:o:netgear:d7000_firmware |
| netgear | d7000 | cpe:2.3:h:netgear:d7000 |
| netgear | jnr1010 firmware | cpe:2.3:o:netgear:jnr1010_firmware |
| netgear | jnr1010 | cpe:2.3:h:netgear:jnr1010 |
| netgear | jr6150 firmware | cpe:2.3:o:netgear:jr6150_firmware |
| netgear | jr6150 | cpe:2.3:h:netgear:jr6150 |
| netgear | jwnr2010 firmware | cpe:2.3:o:netgear:jwnr2010_firmware |
| netgear | jwnr2010 | cpe:2.3:h:netgear:jwnr2010 |
| netgear | pr2000 firmware | cpe:2.3:o:netgear:pr2000_firmware |
| netgear | pr2000 | cpe:2.3:h:netgear:pr2000 |
and 24 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- netgear d6200 firmwarebefore 1.1.00.24
- netgear d7000 firmwarebefore 1.0.1.52
- netgear jnr1010 firmwarebefore 1.1.0.44
- netgear jr6150 firmwarebefore 1.0.1.12
- netgear jwnr2010 firmwarebefore 1.1.0.44
- netgear pr2000 firmwarebefore 1.0.0.20
- netgear r6020 firmwarebefore 1.0.0.26
- netgear r6050 firmwarebefore 1.0.1.12
- netgear r6080 firmwarebefore 1.0.0.26
- netgear r6120 firmwarebefore 1.0.0.36
- netgear r6220 firmwarebefore 1.1.0.60
- netgear r6700 firmwarebefore 1.2.0.12
- netgear r6800 firmwarebefore 1.2.0.12
- netgear r6900 firmwarebefore 1.2.0.12
- netgear wndr3700 firmwarebefore 1.1.0.50
- netgear wnr1000 firmwarebefore 1.1.0.44
- netgear wnr2020 firmwarebefore 1.1.0.44
- netgear wnr2050 firmwarebefore 1.1.0.44
Same product
netgear: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-26908Certain NETGEAR devices are affected by authentication bypass.40Plan
- CVE-2021-45551Certain NETGEAR devices are affected by command injection by an authenticated user.35Monitor
- CVE-2020-26912Certain NETGEAR devices are affected by CSRF.35Monitor
- CVE-2020-26911Certain NETGEAR devices are affected by lack of access control at the function level.35Monitor
- CVE-2017-18727Certain NETGEAR devices are affected by a stack-based buffer overflow by an unauthenticated attacker.35Monitor
- CVE-2017-18725Certain NETGEAR devices are affected by a stack-based buffer overflow by an unauthenticated attacker.35Monitor
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
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:H/I:H/A:H
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.