CVE-2018-19614
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 · uneditedXSS exists in the /cmdexec/cmdexe?cmd= function in Westermo DR-250 Pre-5162 and DR-260 Pre-5162 routers.
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 confidenceCross-site scripting (XSS) vulnerability in Westermo DR-250 and DR-260 routers allows injection of malicious scripts through the /cmdexec/cmdexe?cmd= endpoint. The affected function appears to be a command execution interface that does not properly sanitize user input before rendering it in the web interface.
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 dataall versionsall versionsall versionsCVSS 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.0/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 modelAccess the router's web management interface and look for the device model displayed on the login page, main dashboard, or in the System > Status section. Alternatively, check the physical device label or SNMP sysDescr if accessible.Affected if The device model is Westermo DR-250, DR-260, or MR-260
-
Check the installed firmware versionIn the router's web interface, navigate to System > Status or System > Firmware to view the current firmware version. All versions of the listed models are affected.Affected if The firmware version belongs to Westermo DR-250, DR-260, or MR-260 (all versions are affected)
-
Verify web management interface accessibilityAttempt to access the router's web interface via HTTP or HTTPS on the configured management IP address. Confirm the login page or the / path responds.Affected if The router's web interface is accessible over the network (the XSS requires this attack surface)
-
Confirm the vulnerable endpoint existsAccess the URL path /cmdexec/cmdexe?cmd=test by browsing to http://[router-ip]/cmdexec/cmdexe?cmd=test. If the page loads (with or without command output), the endpoint is present.Affected if The /cmdexec/cmdexe endpoint responds, indicating the vulnerable command execution interface is enabled
You are affected if you have a Westermo DR-250, DR-260, or MR-260 router with its web management interface accessible and the /cmdexec endpoint is present and responsive.
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 when available. Until patched, restrict network access to the router's web management interface and consider placing the device behind a WAF to filter malicious requests.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19614 — 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-19614 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