CVE-2018-21096
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 CSRF. This affects WAC120 before 2.1.7, WAC505 before 5.0.5.4, WAC510 before 5.0.5.4, WNAP320 before 3.7.11.4, WNAP210v2 before 3.7.11.4, WNDAP350 before 3.7.11.4, WNDAP360 before 3.7.11.4, WNDAP660 before 3.7.11.4, WNDAP620 before 2.1.7, WND930 before 2.1.5, and WN604 before 3.3.10.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in NETGEAR wireless access point firmware allows remote attackers to perform unauthorized administrative actions on affected devices by tricking authenticated users into submitting malicious requests.
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< 2.1.7< 5.0.5.4< 5.0.5.4< 3.7.11.4< 3.7.11.4< 3.7.11.4< 3.7.11.4< 3.7.11.4CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/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 the NETGEAR access point modelLog into the device web management interface or check the device label/menu to determine the exact model number (Wac120, Wac505, Wac510, Wnap320, Wnap210, Wndap350, Wndap360, or Wndap660)Affected if The model is one of the eight listed affected products
-
Check the installed firmware versionNavigate to the device web interface Administration > Firmware Upgrade or Status page to view the current firmware version, or use SNMP/CLI commands if availableAffected if The firmware version is lower than 2.1.7 for Wac120, or lower than 5.0.5.4 for Wac505/Wac510, or lower than 3.7.11.4 for Wnap320/Wnap210/Wndap350/Wndap360/Wndap660
-
Verify web management interface is accessibleConfirm the device web administration interface (HTTP/HTTPS on ports 80 or 443) is reachable on the networkAffected if The web interface is exposed and accessible to users or attackers
-
Check for anti-CSRF protectionsInspect the login and configuration pages for the presence of anti-CSRF tokens or SameSite cookie attributes by examining the HTML source or using a web proxy to analyze request headersAffected if No anti-CSRF tokens are present in web forms and requests, making the device vulnerable to CSRF attacks
You are affected if you have a NETGEAR Wac120, Wac505, Wac510, Wnap320, Wnap210, Wndap350, Wndap360, or Wndap660 running firmware below the specified version thresholds and the web management interface is accessible without CSRF protection.
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.1.73.7.11.45.0.5.4
Update affected devices to the specified firmware versions: WAC120/WNDAP620 to 2.1.7+, WAC505/WAC510 to 5.0.5.4+, WNAP320/WNAP210v2/WNDAP350/WNDAP360/WNDAP660 to 3.7.11.4+, WND930 to 2.1.5+, and WN604 to 3.3.10+. If patching is not possible, implement anti-CSRF tokens on web interfaces and monitor for unauthorized configuration changes.
- 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-2018-21096 — 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-2018-21096 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