CVE-2017-18715
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 reflected XSS. This affects EX3700 before 1.0.0.66, EX3800 before 1.0.0.66, EX6100 before 1.0.2.20, EX6120 before 1.0.0.34, EX6150 before 1.0.0.36, EX6200 before 1.0.3.84, and EX7000 before 1.0.0.60.
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 confidenceReflected cross-site scripting (XSS) vulnerability in NETGEAR EX3700, EX3800, EX6100, EX6120, EX6150, EX6200, and EX7000 range extenders. The flaw allows attackers to inject malicious scripts through unsanitized input that gets reflected back in HTTP responses, potentially enabling session hijacking or credential theft.
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.66< 1.0.0.66< 1.0.2.20< 1.0.0.34< 1.0.0.36< 1.0.3.84< 1.0.0.60CVSS 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 your NETGEAR range extender modelLocate the model number on the device label or access the web management interface (typically at http://www.mywifiext.net or http://192.168.1.250) and check the status or settings page for the exact model designation.Affected if The model is one of: EX3700, EX3800, EX6100, EX6120, EX6150, EX6200, or EX7000.
-
Determine the installed firmware versionIn the web management interface, navigate to the Firmware Update or Settings > Status page. The firmware version is typically displayed as a numeric string (for example: 1.0.0.34).Affected if The displayed firmware version falls below the threshold for your specific model.
-
Compare your firmware version against affected rangesMatch your model and version to these thresholds: EX3700/EX3800 < 1.0.0.66, EX6100 < 1.0.2.20, EX6120 < 1.0.0.34, EX6150 < 1.0.0.36, EX6200 < 1.0.3.84, EX7000 < 1.0.0.60.Affected if Your installed version is lower than the version threshold listed for your model.
-
Verify web management interface accessibilityConfirm the web-based management interface is reachable on your local network. This is the attack surface where the XSS vulnerability can be exploited.Affected if The web management interface is accessible and the firmware version is below the patched threshold.
You are affected if you are running any of the listed NETGEAR range extender models with a firmware version below the specified threshold and 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.341.0.0.361.0.0.60
Update affected NETGEAR range extenders to the patched firmware versions: EX3700/EX3800 to 1.0.0.66, EX6100 to 1.0.2.20, EX6120 to 1.0.0.34, EX6150 to 1.0.0.36, EX6200 to 1.0.3.84, and EX7000 to 1.0.0.60. If patching is not immediately possible, restrict web management interface access to trusted networks only.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18715 — 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-18715 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