CVE-2017-18700
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 stored XSS. This affects D6400 before 1.0.0.60, D7000 before 1.0.1.50, D8500 before 1.0.3.29, EX6200 before 1.0.3.84, EX7000 before 1.0.0.60, R6250 before 1.0.4.16, R6300v2 before 1.0.4.18, R6400 before 1.01.32, R6400v2 before 1.0.2.44, R6700 before 1.0.1.36, R6900 before 1.0.1.34, R6900P before 1.3.0.8, R7000 before 1.0.9.14, R7000P before 1.3.0.8, R7100LG before 1.0.0.34, R7300DST before 1.0.0.56, R7900 before 1.0.1.26, R8000 before 1.0.4.4, R8300 before 1.0.2.106, R8500 before 1.0.2.106, R9000 before 1.0.2.52, WNDR3400v3 before 1.0.1.16, WNR3500Lv2 before 1.2.0.46, and WNDR3700v5 before 1.1.0.48.
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 confidenceThis is a stored cross-site scripting (XSS) vulnerability in the web management interface of multiple NETGEAR router models. An attacker can inject malicious JavaScript code into input fields that get stored on the device and executed when administrators access the affected pages. The CVSS 6.1 score indicates the vulnerability is exploitable with low privilege and requires some user interaction.
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.0.60< 1.0.1.50< 1.0.3.29< 1.0.3.84< 1.0.0.60< 1.0.4.16< 1.0.4.18< 1.01.32< 1.0.2.44CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 router modelLocate the model number on the device label on the bottom or back of the router, or log into the web management interface and check the status or settings page for the model nameAffected if The model is one of: D6400, D7000, D8500, Ex6200, Ex7000, R6250, R6300, or R6400
-
Check the installed firmware versionLog into the router web interface (typically at 192.168.1.1) and navigate to the Firmware Update or Router Status page to view the current firmware version. Alternatively, check the administration or settings section for version informationAffected if The firmware version is below the threshold for your model (D6400: < 1.0.0.60, D7000: < 1.0.1.50, D8500: < 1.0.3.29, Ex6200: < 1.0.3.84, Ex7000: < 1.0.0.60, R6250: < 1.0.4.16, R6300: < 1.0.4.18, R6400: < 1.0.2.44 or < 1.01.32)
-
Determine if the web management interface is accessibleVerify whether the router web interface is accessible from the local network or remotely. Check the router settings for Remote Management or Web Management Access options to see if external access is enabledAffected if The web management interface is exposed and accessible (especially remotely), increasing the attack surface for stored XSS injection
Your router is affected if it matches one of the listed models AND its firmware version is below the specified threshold, particularly if the web management interface is 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 data1.0.0.601.0.1.501.0.2.44
Apply the vendor-supplied firmware updates to the specified version thresholds for each affected model. If firmware updates are unavailable, restrict access to the router's web management interface to trusted networks only or disable remote management.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18700 — 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-18700 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