CVE-2019-20487
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 · uneditedAn issue was discovered on NETGEAR WNR1000V4 1.1.0.54 devices. Multiple actions within the WNR1000V4 web management console are vulnerable to an unauthenticated GET request (exploitable directly or through CSRF), as demonstrated by the setup.cgi?todo=save_htp_account URI.
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 confidenceThe NETGEAR WNR1000V4 router firmware 1.1.0.54 contains an authentication bypass vulnerability where sensitive administrative actions in the web management console can be triggered via unauthenticated GET requests to CGI endpoints (e.g., setup.cgi?todo=save_htp_account). The flaw is exploitable directly or through CSRF attacks, allowing remote attackers to perform configuration changes without any credentials.
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.1.0.54CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 device model and firmware versionAccess the router web interface or check the admin page for the exact model number (WNR1000V4) and firmware version (typically under Administration > Firmware Update or Status page)Affected if Device is NETGEAR WNR1000V4 and firmware version equals 1.1.0.54
-
Verify remote web management is enabledCheck the router settings under Advanced > Remote Management (or similar) to see if 'Enable Remote Management' or 'Allow remote access' is turned onAffected if Remote web management is enabled, making the vulnerable CGI interface accessible from external networks
-
Test for unauthenticated CGI endpoint accessSend a GET request to http://[router-ip]/setup.cgi?todo=save_htp_account (or other CGI endpoints) without any authentication headers or credentialsAffected if The request returns a valid response or performs an action without requiring login credentials
-
Monitor for suspicious GET requests to CGI endpointsReview router logs or network traffic for GET requests to /setup.cgi or similar CGI scripts with 'todo=' parameters, especially from unauthenticated sourcesAffected if Unexplained GET requests to CGI endpoints appear in logs without corresponding authentication sessions
The environment is affected if the device is a NETGEAR WNR1000V4 running firmware version 1.1.0.54 AND the web management interface is remotely 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.
From vendor dataApply the vendor-supplied firmware patch when available; prior to patching, disable remote web management access, segment affected devices on isolated VLANs, and monitor for suspicious GET requests to CGI endpoints.
- Consultation2.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 $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20487 — 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-20487 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