Security Advisory

CVE-2022-31800: Phoenix Classic Line Logic Upload

Last updated:
  • CVE-2022-31800

CVE-2022-31800 is missing integrity and authenticity checking of PLC logic (CWE-345) on Phoenix Contact classic line controllers built on ProConOS/ProConOS eCLR: an unauthenticated remote attacker can upload malicious logic and take full control of an ILC, AXC 1050/3050 or RFC 4xx. There is no fix by design. NVD scores it 10.0 (CVSS v2); CERT@VDE scores it 9.8.

Vulnerability summary

CVSS base score

10

Critical severity

EPSS score (FIRST)

1.6%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2022-31800 · Source: NVD

Affected components

ComponentCPEVersion range
Phoenix Contact ILC 1x0, ILC 1x1, ILC 1x1 GSM/GPRS and ILC 3xxcpe:2.3:o:phoenixcontact:ilc1x1_firmware:*:*:*:*:*:*:*:*all firmware versions (NVD, CERT@VDE VDE-2022-025); no fix, mitigations only
Phoenix Contact AXC 1050, AXC 1050 XC and AXC 3050cpe:2.3:o:phoenixcontact:axc_1050_firmware:*:*:*:*:*:*:*:*all firmware versions (NVD, VDE-2022-025); no fix, mitigations only
Phoenix Contact RFC 430 ETH-IB, RFC 450 ETH-IB, RFC 460R PN 3TX, RFC 460R PN 3TX-S, RFC 470 PN 3TX, RFC 470S PN 3TX, RFC 480S PN 4TXcpe:2.3:o:phoenixcontact:rfc_480s_pn_4tx_firmware:*:*:*:*:*:*:*:*all firmware versions (NVD, VDE-2022-025); no fix, mitigations only
Phoenix Contact FC 350 PCI ETH, PC WORX SRT, PC WORX RT BASICcpe:2.3:o:phoenixcontact:pc_worx_srt_firmware:*:*:*:*:*:*:*:*all versions (NVD, VDE-2022-025); no fix, mitigations only

What does this mean for affected devices?

NVD's 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." NVD's only Primary metric is CVSS v2 10.0 (AV:N/AC:L/Au:N/C:C/I:C/A:C); it has no NVD CVSS v3 score. CERT@VDE as CNA scores it CVSS v3.1 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) with CWE-345 (insufficient verification of data authenticity). NVD's CPEs list all firmware of 17 classic line products, and the record was published on 2022-06-21 (NVD).

Why can anyone load logic onto these PLCs?

CERT@VDE VDE-2022-025, released on 21 June 2022, says "the affected devices insufficiently verify uploaded data", and Phoenix Contact's mitigation note explains why there is no patch: "The controller doesn't feature logic integrity and authenticity checks by design." An attacker able to transmit manipulated logic or to manipulate legitimate logic "can execute arbitrary malicious code on the device". Forescout reported it (CERT@VDE CSAF), and CISA's ICSA-22-172-03 of the same day credits Daniel dos Santos and Jos Wetzels of Forescout Technologies and states that no known public exploits specifically target it.

The upload path is the same unauthenticated engineering access tracked as CVE-2019-9201 on TCP port 1962, so the two CVEs together let anyone on the network replace the control program.

How do you protect classic line controllers from CVE-2022-31800?

Every affected product has all firmware versions listed and no fix. Phoenix Contact's mitigations, republished by CISA:

  • Use the controllers only in closed industrial networks, behind a firewall, with the plant divided into OT zones.
  • Keep connections between the engineering tool and the controller in a locally protected environment, or behind VPN for remote access.
  • Do not send project data as a file by email or other transfer without separate integrity and authenticity checks, and store it only in protected environments.

The ILC 1x0 and 1x1 have a further unfixed network flaw, CVE-2021-33541. PLCnext Control, the successor line, gets firmware fixes, for example CVE-2020-12519 and CVE-2021-34570. Our Phoenix Contact PLCnext and classic line security guide covers the zone design for classic controllers and the later Automation Worx logic-integrity advisories.

Is CVE-2022-31800 exploited?

CVE-2022-31800 is not in the CISA KEV catalog as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.01596, the 76th percentile, in the 2026-11-17 dataset (CISA KEV, FIRST EPSS).

How to fix this class of issueNo dedicated SoftWSP guide covers this weakness class; the fix is usually the vendor patch or firmware update referenced above. Our related guide explains how to plan and verify it: NIST SP 800-40 Rev. 4: enterprise patch management planning, explained.

Evidence

  • NVD: unauthenticated remote attacker could upload malicious logic to ProConOS/ProConOS eCLR devices to gain full control; NVD Primary CVSS v2 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C, no NVD v3 score; CERT@VDE CNA CVSS v3.1 9.8; CWE-345 (CERT@VDE); all firmware CPEs of 17 classic line products; published 2022-06-21. — NVD
  • VDE-2022-025 CSAF (2022-06-21): affected devices insufficiently verify uploaded data; attacker can execute arbitrary malicious code; controller doesn't feature logic integrity and authenticity checks by design; all firmware versions of AXC 1050/1050 XC/3050, FC 350 PCI ETH, ILC1x0, ILC1x1, ILC 1x1 GSM/GPRS, ILC 3xx, PC WORX RT BASIC/SRT, RFC 430/450/460R/460R-S/470/470S/480S affected; CVSS 9.8; reported by Forescout. — CERT@VDE VDE-2022-025 (CSAF)
  • ICSA-22-172-03 (2022-06-21): CWE-345, CVSS v3 9.8; mitigations: closed networks, OT zones with firewalls, engineering connections in protected environment or VPN, no project data by email without integrity checks, store project data in protected environments; no known public exploits; reported by Daniel dos Santos and Jos Wetzels of Forescout Technologies. — CISA CSAF ICSA-22-172-03
  • Not in the CISA KEV catalog, version 2026.11.17 (1,782 entries), checked 2026-11-18; the catalog has no Phoenix Contact entry. — CISA KEV
  • EPSS 0.01596, percentile 0.76163, dataset 2026-11-17. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. CERT@VDE VDE-2022-025: Phoenix Contact vulnerability in classic line industrial controllers
  3. CERT@VDE CSAF: VDE-2022-025 (machine-readable advisory)
  4. CISA ICS Advisory ICSA-22-172-03: Phoenix Contact Classic Line Controllers
  5. CISA CSAF: ICSA-22-172-03 (machine-readable advisory)
  6. Phoenix Contact PSIRT
  7. CISA KEV
  8. FIRST EPSS

Frequently asked questions

Will Phoenix Contact release a firmware fix for CVE-2022-31800?

The advisory lists no fix. Phoenix Contact states that the classic line controllers do not feature logic integrity and authenticity checks by design and lists all firmware versions as affected; the remedies are network isolation and protected handling of project data (per CERT@VDE VDE-2022-025 and CISA ICSA-22-172-03).

Which controllers are affected by CVE-2022-31800?

All firmware of the ILC 1x0, ILC 1x1, ILC 1x1 GSM/GPRS, ILC 3xx, AXC 1050, AXC 1050 XC, AXC 3050, RFC 430/450 ETH-IB, RFC 460R PN 3TX and 3TX-S, RFC 470 PN 3TX, RFC 470S PN 3TX, RFC 480S PN 4TX, FC 350 PCI ETH, PC WORX SRT and PC WORX RT BASIC (per VDE-2022-025).

Why is the NVD score 10.0 and not 9.8?

NVD scored this record only under CVSS v2, at 10.0, and has no CVSS v3 score of its own. The 9.8 is the CVSS v3.1 score from CERT@VDE as CNA, which CISA also uses (per NVD and ICSA-22-172-03).

Is CVE-2022-31800 in the CISA KEV catalog?

No, not as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.01596, the 76th percentile, in the 2026-11-17 dataset (per CISA KEV and FIRST EPSS).