CVE-2020-35831
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, RAX120 before 1.0.0.78, RBK50 before 2.3.5.30, RBR50 before 2.3.5.30, RBS50 before 2.3.5.30, XR500 before 2.3.2.56, and XR700 before 1.0.1.10.
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 contain a stored cross-site scripting (XSS) vulnerability in their web management interface. The malicious script is permanently stored on the device and executes when administrative users access the affected functionality, allowing attackers to steal session cookies, perform actions as the authenticated user, or inject additional content.
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< 1.0.0.78< 2.3.5.30< 2.3.5.30CVSS 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 modelLocate the model number on the device label or access the web management interface and look at the top of any admin page for the model name (such as D7800, R7500v2, R7800, R8900, R9000, RAX120, RBK50, or RBR50)Affected if The model is one of the eight affected models listed in the CVE
-
Check the installed firmware versionLog into the router web interface, navigate to Advanced > Administration > Firmware Upgrade, or look for a 'Router Info' or 'Status' page that displays the current firmware versionAffected if The firmware version is lower than the fixed version for your model: D7800 < 1.0.1.56, R7500v2 < 1.0.3.46, R7800 < 1.0.2.68, R8900 < 1.0.4.28, R9000 < 1.0.4.28, RAX120 < 1.0.0.78, RBK50/RBR50 < 2.3.5.30
-
Verify remote web management access statusIn the router interface, check under Advanced > Administration > Remote Management or Remote Access settings to see if remote administrative access is enabledAffected if Remote web management is enabled and the device is reachable over the network, as this allows potential attackers to reach the vulnerable management interface
-
Inspect router configuration for suspicious contentNavigate to settings pages in the web interface (such as network name, SSID, or other input fields) and view the page source or examine saved configurations for unexpected script tags or HTML that may indicate prior exploitationAffected if Unexpected JavaScript tags, script elements, or malformed HTML appear in configuration fields that you did not intentionally set
You are affected if you own one of the eight listed NETGEAR models and your current firmware version is below the specified fixed version 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.561.0.2.68
Update the firmware of affected NETGEAR devices to the specified versions (D7800: 1.0.1.56, R7500v2: 1.0.3.46, R7800: 1.0.2.68, R8900: 1.0.4.28, R9000: 1.0.4.28, RAX120: 1.0.0.78, RBK50/RBR50/RBS50: 2.3.5.30, XR500: 2.3.2.56, XR700: 1.0.1.10) or later. If patching is not possible immediately, restrict administrative interface access to trusted IP addresses only.
- 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-35831 — 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-35831 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