CVE-2021-45533
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 command injection by an authenticated user. This affects EX6120 before 1.0.0.66, EX6130 before 1.0.0.46, EX7000 before 1.0.1.106, EX7500 before 1.0.1.76, EX3700 before 1.0.0.94, EX3800 before 1.0.0.94, RBR850 before 4.6.3.9, RBS850 before 4.6.3.9, and RBK852 before 4.6.3.9.
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 wireless extenders and mesh router systems contain an authenticated command injection vulnerability allowing a remote attacker with valid credentials to execute arbitrary OS commands on the affected device through unsanitized input in the 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.66< 1.0.0.46< 1.0.1.106< 1.0.1.76< 1.0.0.94< 1.0.0.94< 4.6.3.9< 4.6.3.9CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:H/UI:N/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 your NETGEAR device modelLocate the device label on the extender or mesh router, or log into the web management interface and look for the model name in the status or settings pageAffected if The model is one of: Ex6120, Ex6130, Ex7000, Ex7500, Ex3700, Ex3800, Rbr850, or Rbs850
-
Determine the current firmware versionIn the web management interface, navigate to the firmware update or status section to view the installed firmware version. Alternatively, check the device label if the firmware version is printed thereAffected if Unable to determine the firmware version from the device or interface
-
Compare your firmware version against affected rangesMatch your identified model and firmware version against these thresholds: Ex6120 < 1.0.0.66, Ex6130 < 1.0.0.46, Ex7000 < 1.0.1.106, Ex7500 < 1.0.1.76, Ex3700 < 1.0.0.94, Ex3800 < 1.0.0.94, Rbr850 < 4.6.3.9, Rbs850 < 4.6.3.9Affected if Your device model is listed above AND the installed firmware version is below the corresponding threshold
-
Verify web management interface accessibilityAttempt to access the device web interface at the default gateway IP address (typically 192.168.1.1 or 192.168.1.250 for extenders) using a browserAffected if The web management interface is accessible and you can log in with administrator credentials
Your device is affected if it matches one of the eight affected models and runs a firmware version lower than the specified threshold for that model, and the web management interface is accessible with valid credentials.
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.461.0.0.661.0.0.94
Update affected devices to the specified firmware versions (EX6120: 1.0.0.66, EX6130: 1.0.0.46, EX7000: 1.0.1.106, EX7500: 1.0.1.76, EX3700/EX3800: 1.0.0.94, RBR850/RBS850/RBK852: 4.6.3.9) or later, and review administrator accounts for unauthorized access.
EX6120: 1.0.0.66 | EX6130: 1.0.0.46 | EX7000: 1.0.1.106 | EX7500: 1.0.1.76 | EX3700/EX3800: 1.0.0.94 | RBR850/RBS850/RBK852: 4.6.3.9
- 1. Identify the exact NETGEAR device model from the affected list (EX6120, EX6130, EX7000, EX7500, EX3700, EX3800, RBR850, RBS850, or RBK852)
- 2. Access the device web interface or admin panel using administrative credentials
- 3. Navigate to the firmware update or administration section
- 4. Download the appropriate firmware version from the official NETGEAR support site (kb.netgear.com) matching your device model
- 5. Upload and install the firmware update, ensuring power is not interrupted during the process
- 6. After the device reboots, verify the firmware version has been updated to the fixed release or higher
- 7. Confirm the device is functioning normally post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-45533 — 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-45533 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