CVE-2021-45639
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 reflected XSS. This affects CBR40 before 2.5.0.10, EAX20 before 1.0.0.32, EAX80 before 1.0.1.62, EX6120 before 1.0.0.64, EX6130 before 1.0.0.44, EX7000 before 1.0.1.104, EX7500 before 1.0.0.72, R7000 before 1.0.11.110, R7900 before 1.0.4.30, R7960P before 1.4.1.66, R8000 before 1.0.4.62, RAX200 before 1.0.2.102, XR300 before 1.0.3.50, EX3700 before 1.0.0.90, MR60 before 1.0.5.102, R7000P before 1.3.2.126, R8000P before 1.4.1.66, RAX20 before 1.0.1.64, RAX50 before 1.0.2.28, RAX80 before 1.0.3.102, EX3800 before 1.0.0.90, MS60 before 1.0.5.102, R6900P before 1.3.2.126, R7900P before 1.4.1.66, RAX15 before 1.0.1.64, RAX45 before 1.0.2.28, RAX75 before 1.0.3.102, RBR750 before 3.2.16.6, RBR850 before 3.2.16.6, RBS750 before 3.2.16.6, RBS850 before 3.2.16.6, RBK752 before 3.2.16.6, and RBK852 before 3.2.16.6.
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 confidenceReflected XSS vulnerability in NETGEAR router web interfaces. An attacker can craft malicious URLs containing JavaScript payloads that, when clicked by an authenticated user, execute in the context of the router's web session, allowing session hijacking or actions performed on the user's behalf.
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< 2.5.0.10< 1.0.0.32< 1.0.1.62< 1.0.0.64< 1.0.0.44< 1.0.1.104< 1.0.0.72< 1.0.11.110CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 your NETGEAR router modelLog into the router web interface and locate the model number typically displayed on the top of the page or in the Status/Firmware section, or check the physical device labelAffected if The model matches one of the affected models: Cbr40, Eax20, Eax80, Ex6120, Ex6130, Ex7000, Ex7500, or R7000
-
Determine the installed firmware versionIn the router web interface, navigate to the Administration or Advanced section and look for Firmware Version or Router Status informationAffected if The firmware version is lower than the secure threshold for your model (Cbr40 < 2.5.0.10, Eax20 < 1.0.0.32, Eax80 < 1.0.1.62, Ex6120 < 1.0.0.64, Ex6130 < 1.0.0.44, Ex7000 < 1.0.1.104, Ex7500 < 1.0.0.72, R7000 < 1.0.11.110)
-
Confirm the router web management interface is accessibleAttempt to access the router login page by entering the router IP address (commonly 192.168.1.1) in a web browserAffected if The web interface is reachable from the network, meaning an attacker could potentially trick an authenticated user into visiting a malicious URL
-
Verify if remote management is enabledIn the router web interface under Advanced or Administration settings, check the Remote Management or External Access configurationAffected if Remote management is enabled, which could allow exploitation from outside the local network
You are affected if your router model is one of the eight listed models and your installed firmware version falls below the specified secure version threshold, combined with an accessible web interface that could be targeted with malicious URLs.
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.
dbcve · scoped1.0.0.321.0.0.441.0.0.64
Apply vendor firmware updates to all affected devices, upgrading to versions at or above the specified thresholds. Users should avoid clicking untrusted links to router management interfaces until patched.
Firmware version >= 2.5.0.10 for CBR40, >= 1.0.0.32 for EAX20, >= 1.0.1.62 for EAX80, >= 1.0.0.64 for EX6120, >= 1.0.0.44 for EX6130, >= 1.0.1.104 for EX7000, >= 1.0.0.72 for EX7500, >= 1.0.11.110 for R7000 (and corresponding fixed versions for other models as listed in the official advisory)
- Identify the specific NETGEAR device model from the affected list
- Navigate to the NETGEAR support website (support.netgear.com) or the knowledge base (kb.netgear.com)
- Locate the firmware download page for your device model
- Download the latest firmware version that meets or exceeds the fixed version for your device: CBR40: 2.5.0.10+, EAX20: 1.0.0.32+, EAX80: 1.0.1.62+, EX6120: 1.0.0.64+, EX6130: 1.0.0.44+, EX7000: 1.0.1.104+, EX7500: 1.0.0.72+, R7000: 1.0.11.110+
- Access the device's web management interface using an administrator account
- Navigate to the firmware update or administration section
- Upload and apply the downloaded firmware file
- Wait for the device to reboot and verify the firmware version was updated successfully
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-45639 — 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-2021-45639 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