CVE-2023-1205
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 · uneditedNETGEAR Nighthawk WiFi6 Router prior to V1.0.10.94 is vulnerable to cross-site request forgery attacks on all endpoints due to improperly implemented CSRF protections.
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 confidenceNETGEAR Nighthawk WiFi6 Router versions prior to V1.0.10.94 contain improperly implemented CSRF protection across all web interface endpoints, allowing attackers to craft malicious requests that execute unintended administrative actions when a logged-in administrator visits a crafted page.
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.10.94CVSS 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.
-
Access router web interfaceOpen a browser and navigate to the router's admin URL (typically http://routerlogin.net or http://192.168.1.1). Log in with administrator credentials.Affected if You are able to access the admin interface (indicates the web interface is active)
-
Locate firmware versionIn the router web interface, navigate to the Administration, Settings, or Advanced tab. Look for 'Router Update', 'Firmware Version', or 'Software Version' section to find the current firmware build number.Affected if You find a firmware version displayed in the interface
-
Compare against vulnerable versionNote the exact firmware version shown (for example, it may appear as V1.0.10.90 or similar). Compare this version number to the fixed version 1.0.10.94.Affected if The installed firmware version is less than 1.0.10.94 (for example, 1.0.10.90, 1.0.10.88, etc.)
You are affected if your Netgear Rax30 router runs firmware version lower than 1.0.10.94, as this indicates the CSRF protection is not yet fixed.
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.10.94
Update the NETGEAR Nighthawk WiFi6 Router firmware to version V1.0.10.94 or later to obtain the fixed CSRF protections.
Rax30 Firmware version 1.0.10.94
- Obtain firmware version 1.0.10.94 or later from the official NETGEAR support website for the Rax30 router
- Access the router's web-based administration interface
- Navigate to the Administration or Firmware Update section
- Upload and install the firmware update file
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-1205 — 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-2023-1205 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