CVE-2018-16195
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 · uneditedAterm WF1200CR and Aterm WG1200CR (Aterm WF1200CR firmware Ver1.1.1 and earlier, Aterm WG1200CR firmware Ver1.0.1 and earlier) allows an attacker on the same network segment to execute arbitrary OS commands via SOAP interface of UPnP.
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 confidenceThe vulnerability is a command injection flaw in the UPnP SOAP interface of Aterm WF1200CR and WG1200CR routers. An attacker on the same network segment can send malicious SOAP requests to the UPnP service, which lacks proper input sanitization, allowing arbitrary OS command execution with the device's privileges.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:A/AC:L/PR:N/UI:N/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 router modelAccess the router administration web interface and check the device information page, or look at the physical device label for the model number (WF1200CR or WG1200CR)Affected if The device is a Nec Aterm WF1200CR or WG1200CR
-
Check the installed firmware versionLog into the router web interface and navigate to the firmware or system information page. The version is typically displayed as 'Ver X.X.X' or similarAffected if Firmware version is 1.1.1 or earlier on WF1200CR, or 1.0.1 or earlier on WG1200CR
-
Verify if UPnP is enabledIn the router web interface, locate the UPnP settings (usually under Advanced, Network, or NAT settings). Check if the UPnP checkbox is enabled or if the status shows 'ON'Affected if UPnP is currently enabled on the device
-
Confirm network accessibility to the UPnP serviceFrom a device on the same network segment, verify the UPnP service is reachable by attempting to access the SOAP endpoint on port 1900 (UDP) or scanning for UPnP SSDP responsesAffected if The UPnP service is reachable from an untrusted network segment or the router is exposed to non-trusted devices
The device is affected if it is a WF1200CR with firmware 1.1.1 or earlier OR a WG1200CR with firmware 1.0.1 or earlier, and UPnP is enabled and 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 dataApply vendor firmware updates (WF1200CR Ver1.1.2 or later, WG1200CR Ver1.0.2 or later). As an interim measure, disable UPnP on the affected devices and restrict network access to trusted devices only.
- Consultation2.0 h
- Implementation1.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 $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-16195 — 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-16195 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