CVE-2018-19612
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 · uneditedThe /uploadfile? functionality in Westermo DR-250 Pre-5162 and DR-260 Pre-5162 routers allows remote users to upload malicious file types and execute ASP code.
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 /uploadfile? endpoint in Westermo DR-250 Pre-5162 and DR-260 Pre-5162 routers lacks proper validation of uploaded file types, allowing remote attackers to upload malicious files that can be executed as ASP code. This is an unrestricted file upload vulnerability leading to remote code execution (RCE).
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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 Westermo router modelAccess the router's web interface or check the device label/management console to confirm the exact model number (DR-250, DR-260, or MR-260)Affected if The model is Westermo DR-250, DR-260, or MR-260, as all versions of these models are affected by this vulnerability
-
Confirm web management interface is accessibleAttempt to reach the router's web interface via HTTP/HTTPS from a network location - typically on ports 80 or 443, or the configured management portAffected if The web management interface responds and is reachable from your network, which exposes the vulnerable /uploadfile endpoint
-
Check if the /uploadfile endpoint is exposedSend a request to the /uploadfile endpoint (e.g., GET http://<router-ip>/uploadfile) and observe the responseAffected if The endpoint returns a response (even an error) indicating it exists and is reachable, meaning the file upload functionality is exposed
-
Verify if authentication is required for uploadsObserve whether the /uploadfile endpoint prompts for credentials or returns a login page when accessed without valid authenticationAffected if The upload endpoint is accessible without authentication or with default credentials, indicating the vulnerability is exploitable without additional privileges
If the device is a Westermo DR-250, DR-260, or MR-260 router and its web management interface with the /uploadfile endpoint is network-accessible, the environment is affected by CVE-2018-19612.
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 dataRestrict access to the router's web management interface to trusted networks, disable the file upload functionality if not required, and apply vendor firmware updates when available. Implement strict allowlist-based file type validation and ensure uploaded files are stored outside web-accessible directories.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19612 — 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-19612 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