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

> An attacker can inject malicious scripts into the Bandwidth Control Rule Settings page of Netis WF2419 routers via the Description parameter.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Jan 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-w23h-9hfr-j5gp

## What is CVE-2018-5967?

CVE-2018-5967 is a medium-severity cross-site scripting vulnerability in n/a, published on 25 Jan 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Netis WF2419 V2.2.36123 devices allow XSS via the Description parameter on the Bandwidth Control Rule Settings page.

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

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

It affects 1 product.


Products: Netis-Systems Wf2419 Firmware.

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

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

## Is CVE-2018-5967 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-19356](https://insights.sbomify.com/CVE-2019-19356/): Netis WF2419 Devices Remote Code Execution (high 7.5, exploited in the wild)
- [CVE-2018-6391](https://insights.sbomify.com/CVE-2018-6391/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-6190](https://insights.sbomify.com/CVE-2018-6190/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-5967 is a medium-severity cross-site scripting vulnerability in n/a, published on 25 Jan 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-5967 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-5967/ (Markdown: https://insights.sbomify.com/CVE-2018-5967/index.md)
```

## Sources

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

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