CVE-2021-32122
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 EX3700 before 1.0.0.90, EX3800 before 1.0.0.90, EX6120 before 1.0.0.64, and EX6130 before 1.0.0.44.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in NETGEAR EX3700, EX3800, EX6120, and EX6130 WiFi range extenders allows attackers to perform unintended actions by tricking authenticated users into submitting malicious requests to the device's web management 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.0.0.90< 1.0.0.90< 1.0.0.64< 1.0.0.44CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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 extender modelLocate the model number on the device label or check the device status page in the web management interface. Confirm it is one of: EX3700, EX3800, EX6120, or EX6130.Affected if The model is EX3700, EX3800, EX6120, or EX6130.
-
Check the installed firmware versionLog into the web management interface and navigate to the Firmware Update or Status page to view the current firmware version. Alternatively, check the device label or documentation.Affected if The firmware version is less than 1.0.0.90 for EX3700/EX3800, less than 1.0.0.64 for EX6120, or less than 1.0.0.44 for EX6130.
-
Verify the web management interface is accessibleAttempt to access the device's web interface via its IP address (commonly 192.168.1.250 for NETGEAR extenders). Confirm the interface loads and accepts authentication.Affected if The web management interface is active and reachable on the network.
The device is affected if it is an EX3700, EX3800, EX6120, or EX6130 with a firmware version below the threshold AND the web management interface is accessible.
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.441.0.0.641.0.0.90
Update firmware to the latest version provided by NETGEAR: EX3700/EX3800 to 1.0.0.90 or later, EX6120 to 1.0.0.64 or later, EX6130 to 1.0.0.44 or later.
EX3700/EX3800: firmware 1.0.0.90 or later; EX6120: firmware 1.0.0.64 or later; EX6130: firmware 1.0.0.44 or later
- 1. Identify the exact model number of your NETGEAR range extender (EX3700, EX3800, EX6120, or EX6130)
- 2. Access the range extender's web management interface by connecting to its Wi-Fi network and navigating to its IP address (typically 192.168.1.250 or mywifiext.net)
- 3. Log in with your admin credentials
- 4. Navigate to the Firmware Update or Administration section
- 5. Check the current firmware version under the router status or settings page
- 6. If the firmware version is below the fixed version (EX3700/EX3800: < 1.0.0.90, EX6120: < 1.0.0.64, EX6130: < 1.0.0.44), download the latest firmware from the official NETGEAR support website (kb.netgear.com) for your specific model
- 7. In the firmware update section, select the downloaded firmware file and initiate the update
- 8. Wait for the firmware upload and installation to complete - do not power off the device during this process
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-32122 — 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-32122 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