CVE-2019-20691
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCertain NETGEAR devices are affected by CSRF. This affects D3600 before 1.0.0.72, D6000 before 1.0.0.72, EX3700 before 1.0.0.70, EX3800 before 1.0.0.70, EX6000 before 1.0.0.30, EX6100 before 1.0.2.24, EX6120 before 1.0.0.40, EX6130 before 1.0.0.22, EX6150v1 before 1.0.0.42, EX6200 before 1.0.3.88, EX7000 before 1.0.0.66, and WN2500RPv2 before 1.0.1.54.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMultiple NETGEAR wireless routers and range extenders suffer from Cross-Site Request Forgery (CSRF) vulnerabilities due to missing or improper anti-CSRF token validation. An attacker can trick an authenticated administrator into unknowingly submitting malicious requests to the device's web management interface, allowing unauthorized configuration changes.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.0.0.72< 1.0.0.72< 1.0.0.70< 1.0.0.70< 1.0.0.30< 1.0.2.24< 1.0.0.40< 1.0.0.22CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the NETGEAR device modelLocate the model number on the device label or check the web management interface (typically at 192.168.1.1) under Router Status or Administration > Router InformationAffected if The model is one of: D3600, D6000, Ex3700, Ex3800, Ex6000, Ex6100, Ex6120, or Ex6130
-
Check the installed firmware versionIn the router web interface, navigate to Administration > Firmware Update or Router Status page and note the displayed firmware version numberAffected if The firmware version is lower than the threshold for your model: D3600/D6000 < 1.0.0.72, Ex3700/Ex3800 < 1.0.0.70, Ex6000 < 1.0.0.30, Ex6100 < 1.0.0.24, Ex6120 < 1.0.0.40, or Ex6130 < 1.0.0.22
-
Verify if the web management interface is accessibleAttempt to access the router's web interface from the network using its IP address (commonly 192.168.1.1). Check if HTTP/HTTPS management is enabled under Administration > Remote ManagementAffected if The web management interface is reachable from network segments where untrusted users could potentially trigger malicious requests
-
Confirm administrator session handlingLog into the router web interface and examine whether the application validates anti-CSRF tokens on configuration change forms. This typically requires examining HTTP requests/responses when submitting settingsAffected if The router does not validate anti-CSRF tokens on state-changing requests (forms that modify settings)
You are affected if your NETGEAR device model matches one of the eight affected products AND its firmware version is below the specified threshold for that model.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1.0.0.221.0.0.301.0.0.40
Apply the vendor-provided firmware updates (specific versions listed per model) to all affected devices. If firmware updates are unavailable, restrict administrative access to trusted networks and educate users about not clicking untrusted links while logged into router admin panels.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20691 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-20691 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data