CVE-2019-20707
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 R7800 before 1.0.2.60 and XR500 before 2.3.2.32.
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 confidenceAuthenticated command injection vulnerability in NETGEAR R7800 (before firmware 1.0.2.60) and XR500 (before firmware 2.3.2.32) routers allows an authenticated attacker to execute arbitrary operating system commands via unspecified vectors 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.2.60< 2.3.2.32CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/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 router modelLog into the router web management interface and check the device information page, or look at the physical device label to confirm the model is Netgear R7800 or XR500Affected if Model is R7800 or XR500 and version cannot be determined or is below threshold
-
Determine installed firmware version on R7800Access router web interface, go to Administration > Firmware Update or Advanced > Administration > Router Update, note the current firmware version displayedAffected if Firmware version is below 1.0.2.60
-
Determine installed firmware version on XR500Access router web interface, go to Administration > Firmware Update or Advanced > Administration > Router Update, note the current firmware version displayedAffected if Firmware version is below 2.3.2.32
-
Check firmware via command line (alternative)If you have telnet or SSH access to the router, run 'cat /proc/version' or 'nvram get firmware_version' to retrieve the installed firmware versionAffected if Returned version is below 1.0.2.60 (R7800) or below 2.3.2.32 (XR500)
The device is affected if it is a Netgear R7800 running firmware below 1.0.2.60, or an XR500 running firmware below 2.3.2.32, and the attacker can authenticate to the web management interface.
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.
From vendor data1.0.2.602.3.2.32
Update router firmware to version 1.0.2.60 or later for R7800, and version 2.3.2.32 or later for XR500. If updates are unavailable, minimize exposure by restricting administrative access to trusted networks and implementing strong authentication.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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 $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20707 — 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-20707 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