# CVE-2022-22511: WAGO PLCs WBM vulnerable to reflected XSS

> An authorized attacker can execute reflected XSS on WAGO PLC web management pages to access confidential information on connected PCs.

- **Severity:** Medium 5.4 (`CVSS:3.1/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:** 9 Mar 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-9vh8-h9vp-88fv

## What is CVE-2022-22511?

CVE-2022-22511 is a medium-severity cross-site scripting vulnerability in WAGO Compact Controller CC100 (751-9301), published on 9 Mar 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Various configuration pages of the device are vulnerable to reflected XSS (Cross-Site Scripting) attacks. An authorized attacker with user privileges may use this to gain access to confidential information on a PC that connects to the WBM after it has been compromised.

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

## Which versions are affected by CVE-2022-22511?

It affects 25 products.


Products: Wago 750-8100 Firmware, Wago 750-8101\/025-000 Firmware, Wago 750-8101 Firmware, Wago 750-8102\/025-000 Firmware, Wago 750-8102 Firmware, Wago 750-8202\/000-012 Firmware, Wago 750-8202\/000-022 Firmware, Wago 750-8202\/025-000 Firmware, Wago 750-8202\/025-001 Firmware, Wago 750-8202 Firmware, Wago 750-82 Firmware, Wago 751-9301 Firmware, Wago 752-8303\/8000-002 Firmware, Wago 762-4205\/8000-002 Firmware, Wago 762-4206\/8000-002 Firmware, Wago 762-4305\/8000-002 Firmware, Wago 762-4306\/8000-002 Firmware, Wago 762-5205\/8000-001 Firmware, Wago 762-5206\/8000-001 Firmware, Wago 762-5305\/8000-002 Firmware and 5 more.

## How do I fix CVE-2022-22511?

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

## Is CVE-2022-22511 being exploited?

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

## Other vulnerabilities in WAGO Compact Controller CC100 (751-9301)

- [CVE-2021-34569](https://insights.sbomify.com/CVE-2021-34569/): WAGO I/O-Check Service prone to Out-of-bounds Write (critical 9.8)
- [CVE-2021-34566](https://insights.sbomify.com/CVE-2021-34566/): WAGO I/O-Check Service prone to Memory Overflow (critical 9.1)
- [CVE-2021-34567](https://insights.sbomify.com/CVE-2021-34567/): WAGO I/O-Check Service prone to Out-of-bounds Read (high 8.2)
- [CVE-2021-34568](https://insights.sbomify.com/CVE-2021-34568/): WAGO I/O-Check Service prone to Allocation of Resources Without Limits or Throttling (high 7.5)
- [CVE-2022-3281](https://insights.sbomify.com/CVE-2022-3281/): WAGO: multiple products - Loss of MAC-Address-Filtering after reboot (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-22511 and fix it if it is affected.

What it is: CVE-2022-22511 is a medium-severity cross-site scripting vulnerability in WAGO Compact Controller CC100 (751-9301), published on 9 Mar 2022. 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-2022-22511 in the wild and no public exploit code.

Affected product: WAGO Compact Controller CC100 (751-9301). 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-2022-22511/ (Markdown: https://insights.sbomify.com/CVE-2022-22511/index.md)
```

## Sources

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

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