CVE-2018-16193
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 · uneditedCross-site scripting vulnerability in Aterm WF1200CR and Aterm WG1200CR (Aterm WF1200CR firmware Ver1.1.1 and earlier, Aterm WG1200CR firmware Ver1.0.1 and earlier) allows authenticated attackers to inject arbitrary web script or HTML via unspecified vectors.
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 confidenceStored cross-site scripting (XSS) vulnerability in the Aterm WF1200CR and WG1200CR router web interface allows authenticated attackers to inject malicious JavaScript or HTML through unsanitized input fields. The vulnerability exists in the firmware web management interface prior to Ver1.1.1 (WF1200CR) and Ver1.0.1 (WG1200CR).
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.1.1<= 1.0.1CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/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 modelAccess the router web management interface and check the device status page, or look for the model number on the physical device label. The vulnerable models are Aterm WF1200CR and WG1200CR.Affected if The device is a Nec Aterm WF1200CR or WG1200CR model.
-
Check the firmware versionLog into the router web interface and navigate to the firmware or system information page. Record the displayed firmware version number.Affected if Firmware version is 1.1.1 or earlier for WF1200CR, or 1.0.1 or earlier for WG1200CR.
-
Verify web interface accessibilityConfirm the router web management interface (typically accessible at the default gateway IP address) is reachable from your network.Affected if The administrative web interface is exposed and accessible.
-
Inspect input fields for unexpected contentNavigate to configuration fields such as device name, SSID settings, or other user-configurable text inputs. View the page source or inspect the HTML to check for any injected script tags or unexpected HTML attributes that may indicate prior exploitation.Affected if Unexpected script tags, HTML elements, or encoded characters are present in the configuration fields or their rendered output.
If the device is a WF1200CR with firmware 1.1.1 or earlier, or a WG1200CR with firmware 1.0.1 or earlier, and the web interface is accessible, the environment is potentially affected by this stored XSS vulnerability.
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 dataUpgrade router firmware to the latest version (Ver1.1.2 or later for WF1200CR, Ver1.0.2 or later for WG1200CR). If upgrading is not immediately possible, restrict administrative access to trusted networks and implement additional input validation at the network perimeter.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-16193 — 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-16193 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