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

> Cross-site scripting vulnerability in WAGO Ethernet Controllers allows attackers to inject scripts via SNMP configuration fields.

- **Severity:** Medium 6.1 (`CVSS:3.1/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:** 12 Oct 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-wrg3-m8rq-ffh7

## What is CVE-2018-16210?

CVE-2018-16210 is a medium-severity cross-site scripting vulnerability in n/a, published on 12 Oct 2018. 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

WAGO 750-88X and WAGO 750-89X Ethernet Controller devices, versions 01.09.18(13) and before, have XSS in the SNMP configuration via the webserv/cplcfg/snmp.ssi SNMP_DESC or SNMP_LOC_SNMP_CONT field.

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

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

It affects 14 products.


Products: Wago 750-352 Firmware, Wago 750-362 Firmware, Wago 750-363 Firmware, Wago 750-823 Firmware, Wago 750-831 Firmware, Wago 750-832 Firmware, Wago 750-852 Firmware, Wago 750-862 Firmware, Wago 750-880 Firmware, Wago 750-881 Firmware, Wago 750-889 Firmware, Wago 750-890 Firmware, Wago 750-891 Firmware, Wago Wago 750-881 Ethernet Controller Devices Firmware.

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

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

## Is CVE-2018-16210 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-16210 is a medium-severity cross-site scripting vulnerability in n/a, published on 12 Oct 2018. 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-16210 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-16210/ (Markdown: https://insights.sbomify.com/CVE-2018-16210/index.md)
```

## Sources

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

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