# CVE-2022-31800: Insufficient Verification of Data Vulnerability in PHOENIX CONTACT classic line industrial controllers

> Unauthenticated attackers can upload malicious logic to PHOENIX CONTACT industrial controllers to gain full device control.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jun 2022
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-m7x4-j34m-52hc

## What is CVE-2022-31800?

CVE-2022-31800 is a critical code injection vulnerability in PHOENIX CONTACT AXC 1050, published on 21 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unauthenticated, remote attacker could upload malicious logic to devices based on ProConOS/ProConOS eCLR in order to gain full control over the device.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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

It affects 17 products.


Products: Phoenixcontact Axc 1050 Firmware, Phoenixcontact Axc 1050 Xc Firmware, Phoenixcontact Axc 3050 Firmware, Phoenixcontact Fc 350 Pci Eth Firmware, Phoenixcontact Ilc1x0 Firmware, Phoenixcontact Ilc1x1 Firmware, Phoenixcontact Ilc 1x1 Gsm\/Gprs Firmware, Phoenixcontact Ilc 3xx Firmware, Phoenixcontact Pc Worx Rt Basic Firmware, Phoenixcontact Pc Worx Srt Firmware, Phoenixcontact Rfc 430 Eth-Ib Firmware, Phoenixcontact Rfc 450 Eth-Ib Firmware, Phoenixcontact Rfc 460r Pn 3tx-S Firmware, Phoenixcontact Rfc 460r Pn 3tx Firmware, Phoenixcontact Rfc 470 Pn 3tx Firmware, Phoenixcontact Rfc 470s Pn 3tx Firmware, Phoenixcontact Rfc 480s Pn 4tx Firmware.

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

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

## Is CVE-2022-31800 being exploited?

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

## Other vulnerabilities in PHOENIX CONTACT AXC 1050

- [CVE-2019-9201](https://insights.sbomify.com/CVE-2019-9201/): Missing authorization in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-31800 is a critical code injection vulnerability in PHOENIX CONTACT AXC 1050, published on 21 Jun 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-31800 in the wild and no public exploit code.

Affected product: PHOENIX CONTACT AXC 1050. 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-31800/ (Markdown: https://insights.sbomify.com/CVE-2022-31800/index.md)
```

## Sources

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

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