# CVE-2018-25090: Wago: Improper Neutralization of Input During Web Page Generation in multiple devices

> Unauthenticated remote attackers can execute cross-site scripting attacks on WAGO industrial controllers, compromising confidentiality and integrity.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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:** 13 Mar 2024
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-fr2x-v6g7-3mwv

## What is CVE-2018-25090?

CVE-2018-25090 is a medium-severity cross-site scripting vulnerability in WAGO Controller BACnet MS/TP, published on 13 Mar 2024. 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

An unauthenticated remote attacker can use an XSS attack due to improper neutralization of input during web page generation. User interaction is required. This leads to a limited impact of confidentiality and integrity but no impact of availability.

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

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


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

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

## Is CVE-2018-25090 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-25090 is a medium-severity cross-site scripting vulnerability in WAGO Controller BACnet MS/TP, published on 13 Mar 2024. 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-25090 in the wild and no public exploit code.

Affected product: WAGO Controller BACnet MS/TP. 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-25090/ (Markdown: https://insights.sbomify.com/CVE-2018-25090/index.md)
```

## Sources

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

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