CVE-2019-20730
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 SQL injection. This affects D3600 before 1.0.0.68, D6000 before 1.0.0.68, D6200 before 1.1.00.28, D6220 before 1.0.0.40, D6400 before 1.0.0.74, D7000 before 1.0.1.60, D7000v2 before 1.0.0.74, D7800 before 1.0.1.34, D8500 before 1.0.3.39, DC112A before 1.0.0.40, EX8000 before 1.0.0.118, JR6150 before 1.0.1.18, R6050 before 1.0.1.18, R6220 before 1.1.0.66, R6250 before 1.0.4.26, R6300v2 before 1.0.4.24, R6400 before 1.0.1.36, R6400v2 before 1.0.2.52, R6700 before 1.0.1.44, R6700v2 before 1.2.0.16, R6800 before 1.2.0.16, R6900v2 before 1.2.0.16, R6900 before 1.0.1.44, R7000 before 1.0.9.26, R6900P before 1.3.0.20, R7000P before 1.3.0.20, R7100LG before 1.0.0.40, R7300DST before 1.0.0.62, R7500 before 1.0.0.118, R7500v2 before 1.0.3.26, R7800 before 1.0.2.40, R7900 before 1.0.2.10, R8000 before 1.0.4.12, R7900P before 1.3.0.10, R8000P before 1.3.0.10, R8300 before 1.0.2.116, R8500 before 1.0.2.116, R8900 before 1.0.3.6, R9000 before 1.0.3.10, WNDR3700v4 before 1.0.2.102, WNDR3700v5 before 1.1.0.54, WNDR4300v1 before 1.0.2.98, WNDR4300v2 before 1.0.0.56, and WNDR4500v3 before 1.0.0.56.
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 confidenceSQL injection vulnerability in NETGEAR router web management interfaces allows remote attackers to execute arbitrary SQL queries via unsanitized input parameters. This affects the administration panel of numerous NETGEAR device models running firmware versions prior to the specified patch thresholds.
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.68< 1.0.0.68< 1.1.00.28< 1.0.0.40< 1.0.0.74< 1.0.1.60< 1.0.0.74< 1.0.1.34< 1.0.3.39CVSS 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
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 router admin panel (typically 192.168.1.1) and check the status or administration pageAffected if The device is a D3600, D6000, D6200, D6220, D6400, D7000, D7800, or D8500 model
-
Check the installed firmware versionIn the router web admin panel, navigate to the Administration or Firmware Update section and note the displayed firmware version numberAffected if The firmware version is below 1.0.0.68 (D3600/D6000), 1.1.00.28 (D6200), 1.0.0.40 (D6220), 1.0.0.74 (D6400), 1.0.1.60 or 1.0.0.74 (D7000), 1.0.1.34 (D7800), or 1.0.3.39 (D8500)
-
Verify if web management interface is enabledIn the router settings, look for 'Remote Management', 'Web Management Access', or 'Administration' settings and check whether the web interface is turned onAffected if The router web management interface is enabled and accessible
You are affected if you own one of the listed NETGEAR models AND your firmware version is below the threshold AND the web management interface is enabled.
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.401.0.0.681.0.0.74
Apply vendor-supplied firmware updates to all affected devices. If updates are unavailable, restrict or disable remote web management access and isolate devices on isolated network segments.
Firmware version >= 1.0.0.68 for D3600/D6000; >= 1.1.00.28 for D6200; >= 1.0.0.40 for D6220; >= 1.0.0.74 for D6400; >= 1.0.1.60 for D7000 (or >= 1.0.0.74 for D7000v2); >= 1.0.1.34 for D7800; >= 1.0.3.39 for D8500
- 1. Identify the exact NETGEAR router model number (e.g., D3600, D7000, R7000)
- 2. Check the current firmware version by logging into the router web interface and navigating to Advanced > Administration > Firmware Update
- 3. Visit the NETGEAR support page (support.netgear.com) and search for your specific model number
- 4. Locate the firmware download section and download the latest firmware version that matches or exceeds the fixed version for your model: D3600/D6000: 1.0.0.68, D6200: 1.1.00.28, D6220: 1.0.0.40, D6400: 1.0.0.74, D7000: 1.0.1.60 (v2: 1.0.0.74), D7800: 1.0.1.34, D8500: 1.0.3.39
- 5. In the router's web interface, go to Advanced > Administration > Firmware Update > Upload
- 6. Select the downloaded firmware file and click Upload to begin the upgrade process
- 7. Wait for the firmware to upload and install - do not power off the router during this process
- 8. The router will automatically reboot; log back in and verify the new firmware version is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20730 — 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-2019-20730 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