CVE-2020-35839
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 D7800 before 1.0.1.56, R7500v2 before 1.0.3.46, R7800 before 1.0.2.68, R8900 before 1.0.4.28, R9000 before 1.0.4.28, XR500 before 2.3.2.56, XR700 before 1.0.1.10, and RAX120 before 1.0.0.78.
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 (D7800, R7500v2, R7800, R8900, R9000, XR500, XR700, RAX120) contain a stored cross-site scripting vulnerability in their web management interface. An authenticated attacker can inject malicious JavaScript code that persists on the device and executes when other users access the affected page, potentially allowing session hijacking or credential theft.
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.1.56< 1.0.3.46< 1.0.2.68< 1.0.4.28< 1.0.4.28< 2.3.2.56< 1.0.1.10< 1.0.0.78CVSS 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
- High
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/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 your NETGEAR router modelLook at the device label on the router or access the web management interface and check the status or maintenance page for the model numberAffected if Your device model is D7800, R7500v2, R7800, R8900, R9000, XR500, XR700, or RAX120
-
Check the installed firmware versionLog into the web management interface, navigate to the Firmware Update or Administration section, and record the current firmware version displayedAffected if The firmware version is lower than 1.0.1.56 for D7800, 1.0.3.46 for R7500v2, 1.0.2.68 for R7800, 1.0.4.28 for R8900/R9000, 2.3.2.56 for XR500, 1.0.1.10 for XR700, or 1.0.0.78 for RAX120
-
Confirm web management interface is accessibleAttempt to access the router's web interface by entering the router's IP address in a web browserAffected if You have administrator access to the router's web interface and the firmware version falls within the affected ranges
You are affected if your NETGEAR router model matches one of the eight listed models and your current 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.781.0.1.101.0.1.56
Update each affected device to the specified firmware version: D7800 to 1.0.1.56, R7500v2 to 1.0.3.46, R7800 to 1.0.2.68, R8900/R9000 to 1.0.4.28, XR500 to 2.3.2.56, XR700 to 1.0.1.10, and RAX120 to 1.0.0.78.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-35839 — 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-35839 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