# CVE-2022-3281: WAGO: multiple products - Loss of MAC-Address-Filtering after reboot

> Remote attackers can bypass MAC address filtering after a reboot, gaining unauthorized network access to protected segments in WAGO industrial devices.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Oct 2022
- **Updated:** 10 May 2025
- **Also known as:** GHSA-9qfw-f49w-5jg7

## What is CVE-2022-3281?

CVE-2022-3281 is a high-severity vulnerability in WAGO 750-81xx/xxx-xxx Series PFC100/PFC200, published on 17 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WAGO Series PFC100/PFC200, Series Touch Panel 600, Compact Controller CC100 and Edge Controller in multiple versions are prone to a loss of MAC-Address-Filtering after reboot. This may allow an remote attacker to circumvent the reach the network that should be protected by the MAC address filter.

Weakness: CWE-440 (Expected Behavior Violation)

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

It affects 78 products.


Products: Wago 750-8100 Firmware, Wago 750-8101\/000-010 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-011 Firmware, Wago 750-8202\/000-012 Firmware, Wago 750-8202\/000-022 Firmware, Wago 750-8202\/040-000 Firmware, Wago 750-8206\/025-000 Firmware, Wago 750-8206\/025-001 Firmware, Wago 750-8206\/040-000 Firmware, Wago 750-8206\/040-001 Firmware, Wago 750-8206 Firmware, Wago 750-8207\/025-000 Firmware, Wago 750-8207\/025-001 Firmware, Wago 750-8207 Firmware, Wago 750-8208\/025-000 Firmware, Wago 750-8208\/025-001 Firmware and 58 more.

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

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

## Is CVE-2022-3281 being exploited?

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

## Other vulnerabilities in WAGO 750-81xx/xxx-xxx Series PFC100/PFC200

- [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-22511](https://insights.sbomify.com/CVE-2022-22511/): WAGO PLCs WBM vulnerable to reflected XSS (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3281 is a high-severity vulnerability in WAGO 750-81xx/xxx-xxx Series PFC100/PFC200, published on 17 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-3281 in the wild and no public exploit code.

Affected product: WAGO 750-81xx/xxx-xxx Series PFC100/PFC200. 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-3281/ (Markdown: https://insights.sbomify.com/CVE-2022-3281/index.md)
```

## Sources

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

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