CVE-2017-18863
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 execution via a PHP form. This affects WN604 3.3.3 and earlier, WNAP210v2 3.5.20.0 and earlier, WNAP320 3.5.20.0 and earlier, WNDAP350 3.5.20.0 and earlier, WNDAP360 3.5.20.0 and earlier, WNDAP620 2.0.11 and earlier, WNDAP660 3.5.20.0 and earlier, WND930 2.0.11 and earlier, and WAC120 2.0.7 and earlier.
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 · moderate confidenceMultiple NETGEAR wireless access point devices contain a command injection vulnerability where user-supplied input from a PHP form is not properly sanitized, allowing authenticated attackers to execute arbitrary operating system commands on the affected device.
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< 3.3.3< 3.5.20.0< 3.5.20.0< 3.5.20.0< 3.5.20.0< 2.0.11< 3.5.20.0< 2.0.11CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
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 the NETGEAR device modelLocate the device label on the physical hardware or check the web admin interface for the model number (typically displayed on the dashboard or status page)Affected if The device is one of: Wn604, Wnap210, Wnap320, Wndap350, Wndap360, Wndap620, Wndap660, or Wnd930
-
Determine the installed firmware versionLog into the web administrative interface and navigate to the Status or Maintenance section to view the firmware version; alternatively, check the device label or use SNMP if availableAffected if The firmware version is below the threshold for your model: Wn604 < 3.3.3, Wnap210 < 3.5.20.0, Wnap320 < 3.5.20.0, Wndap350 < 3.5.20.0, Wndap360 < 3.5.20.0, Wndap620 < 2.0.11, Wndap660 < 3.5.20.0, or Wnd930 < 2.0.11
-
Verify administrative interface accessibilityAttempt to reach the device web interface from an untrusted network segment using http or https to port 80 or 443; check firewall rules and ACLs for the device subnetAffected if The administrative web interface is accessible from networks outside the trusted management VLAN
-
Review network exposure and access controlsExamine network segmentation, VLAN configuration, and access control lists to determine if the management interface is isolated from guest or untrusted network segmentsAffected if The device management interface is reachable from network segments with untrusted users
You are affected if your device model matches one of the eight listed models AND the installed firmware version is below the specified threshold for that model, AND the administrative interface is accessible from an untrusted network.
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 data2.0.113.3.33.5.20.0
Apply vendor-supplied firmware updates for affected models; if no patched firmware is available, restrict administrative interface access to trusted networks and implement network segmentation to limit exposure.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18863 — 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-2017-18863 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