CVE-2020-35840
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 stored XSS. This affects D6200 before 1.1.00.38, D7000 before 1.0.1.78, JNR1010v2 before 1.1.0.62, JR6150 before 1.0.1.24, JWNR2010v5 before 1.1.0.62, R6020 before 1.0.0.42, R6050 before 1.0.1.24, R6080 before 1.0.0.42, R6120 before 1.0.0.66, R6220 before 1.1.0.100, R6260 before 1.1.0.76, WNR1000v4 before 1.1.0.62, WNR2020 before 1.1.0.62, and WNR2050 before 1.1.0.62.
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 router models (D6200, D7000, JNR1010v2, JR6150, JWNR2010v5, R6020, R6050, R6080, R6120, R6220, R6260, WNR1000v4, WNR2020, WNR2050) are vulnerable to stored cross-site scripting (XSS) in the web management interface. The vulnerability allows authenticated attackers to inject malicious scripts that persist on the device and execute in the browsers of other users accessing the router's admin interface.
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.1.00.38< 1.0.1.78< 1.1.0.62< 1.0.1.24< 1.1.0.62< 1.0.0.42< 1.0.1.24< 1.0.0.42CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 router modelCheck the product label on the router chassis or log into the web management interface and navigate to the Status or Advanced > Administration > Router Information page to view the Model numberAffected if The model is one of: D6200, D7000, JNR1010v2, JR6150, JWNR2010v5, R6020, R6050, R6080, R6120, R6220, R6260, WNR1000v4, WNR2020, or WNR2050
-
Check the installed firmware versionIn the router web interface, go to Status or Advanced > Administration > Router Information and locate the Firmware Version fieldAffected if The firmware version cannot be determined or is not visible in the standard interface locations
-
Compare firmware version against affected rangesMatch your router model and firmware version to the affected version list: D6200 < 1.1.00.38, D7000 < 1.0.1.78, JNR1010v2 < 1.1.0.62, JR6150 < 1.0.1.24, JWNR2010v5 < 1.1.0.62, R6020 < 1.0.0.42, R6050 < 1.0.1.24, R6080 < 1.0.0.42Affected if Your exact firmware version is below the version threshold for your specific model as listed above
-
Verify administrative access exposureIn the router web interface under Advanced > Remote Management or Administration > Remote Management, check whether remote administrative access is enabled and from which IP addressesAffected if Remote management is enabled and accessible from untrusted networks, increasing the attack surface for authenticated XSS exploitation
You are affected if your router model matches one of the listed models AND your firmware version is below the version threshold for that model, especially if the admin interface is accessible to untrusted users.
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.421.0.1.241.0.1.78
Update router firmware to the specified version or later for each affected model. If firmware updates are unavailable, restrict administrative interface access to trusted users only and disable remote management if not required.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-35840 — 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-2020-35840 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