# CVE-2018-19614: Cross-site scripting in n/a

> Cross-site scripting in Westermo DR-250 and DR-260 routers allows attackers to execute arbitrary scripts in the context of the management interface.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 May 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h8q4-p8r2-jmmm

## What is CVE-2018-19614?

CVE-2018-19614 is a medium-severity cross-site scripting vulnerability in n/a, published on 23 May 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

XSS exists in the /cmdexec/cmdexe?cmd= function in Westermo DR-250 Pre-5162 and DR-260 Pre-5162 routers.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2018-19614?

It affects 3 products.


Products: Westermo Dr-250 Firmware, Westermo Dr-260 Firmware, Westermo Mr-260 Firmware.

## How do I fix CVE-2018-19614?

No fix has been published for CVE-2018-19614 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-19614 being exploited?

There is no known exploitation of CVE-2018-19614 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2018-19612](https://insights.sbomify.com/CVE-2018-19612/): File upload in n/a (high 8.8)
- [CVE-2018-19613](https://insights.sbomify.com/CVE-2018-19613/): Cross-site request forgery in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-19614 and fix it if it is affected.

What it is: CVE-2018-19614 is a medium-severity cross-site scripting vulnerability in n/a, published on 23 May 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-19614 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-19614/ (Markdown: https://insights.sbomify.com/CVE-2018-19614/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-19614
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-19614
- OSV: https://osv.dev/vulnerability/CVE-2018-19614

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-19614/
Summaries are generated and may contain mistakes; the official description above is the record.