CVE-2021-45658
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 server-side injection. This affects D7800 before 1.0.1.58, DM200 before 1.0.0.66, EX2700 before 1.0.1.56, EX6150v2 before 1.0.1.86, EX6100v2 before 1.0.1.86, EX6200v2 before 1.0.1.78, EX6250 before 1.0.0.110, EX6410 before 1.0.0.110, EX6420 before 1.0.0.110, EX6400v2 before 1.0.0.110, EX7300 before 1.0.2.144, EX6400 before 1.0.2.144, EX7320 before 1.0.0.110, EX7300v2 before 1.0.0.110, R7500v2 before 1.0.3.48, R7800 before 1.0.2.68, R8900 before 1.0.5.2, R9000 before 1.0.5.2, RAX120 before 1.0.1.90, RBK40 before 2.5.1.16, RBK20 before 2.5.1.16, RBR20 before 2.5.1.16, RBS20 before 2.5.1.16, RBK50 before 2.5.1.16, RBR50 before 2.5.1.16, RBS50 before 2.5.1.16, RBS50Y before 2.6.1.40, WN3000RPv2 before 1.0.0.78, WN3000RPv3 before 1.0.2.80, WNR2000v5 before 1.0.0.72, XR500 before 2.3.2.56, and XR700 before 1.0.1.20.
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 analysisUntrusted input crosses into a downstream interpreter — SQL, a shell, an HTML page, an LDAP query — without being kept separate from the commands around it, so the attacker's data is read as instructions. This is the parent class behind SQL injection, cross-site scripting, and command injection alike. The durable fix is the same everywhere: keep data and code apart at every boundary, using parameterisation or context-aware encoding rather than building interpreted strings by concatenation.
General guidance for the injection class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
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.58< 1.0.0.66< 1.0.1.56< 1.0.1.86< 1.0.1.86< 1.0.1.78< 1.0.0.110< 1.0.0.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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.661.0.0.1101.0.1.56
Firmware upgrade to version 1.0.1.58 (D7800), 1.0.0.66 (DM200), 1.0.1.56 (EX2700), 1.0.1.86 (EX6150v2/EX6100v2), 1.0.1.78 (EX6200v2), 1.0.0.110 (EX6250/EX6410/EX7320/EX7300v2), 1.0.2.144 (EX7300/EX6400), or later respective versions as listed in the advisory
- 1. Identify the exact NETGEAR device model number from the affected list (D7800, DM200, EX2700, EX6150v2, EX6100v2, EX6200v2, EX6250, EX6410, EX6420, EX6400v2, EX7300, EX6400, EX7320, EX7300v2, R7500v2, R7800, R8900, R9000, RAX120, RBK40, RBK20, RBR20, RBS20, RBK50, RBR50, RBS50, RBS50Y, WN3000RPv2, WN3000RPv3, WNR2000v5, XR500, XR700)
- 2. Access the device web interface or NETGEAR router app to check the current firmware version
- 3. Visit the NETGEAR support site (support.netgear.com) and search for the specific device model
- 4. Navigate to the Downloads/Firmware section for the device
- 5. Download the firmware version that matches or exceeds the fixed version: D7800: 1.0.1.58, DM200: 1.0.0.66, EX2700: 1.0.1.56, EX6150v2/EX6100v2: 1.0.1.86, EX6200v2: 1.0.1.78, EX6250/EX6410/EX7320/EX7300v2: 1.0.0.110, EX7300/EX6400: 1.0.2.144, R7500v2: 1.0.3.48, R7800: 1.0.2.68, R8900/R9000: 1.0.5.2, RAX120: 1.0.1.90, RBK40/RBK20/RBR20/RBS20/RBK50/RBR50/RBS50: 2.5.1.16, RBS50Y: 2.6.1.40, WN3000RP
- 6. In the device web interface, go to Administration > Firmware Update or Router Update section
- 7. Upload and apply the downloaded firmware file
- 8. Wait for the update to complete and the device to reboot
Generated from the published advisory — verify against the referenced sources before acting.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-45658 — 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-45658 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