CVE-2019-9201 is missing authentication (CWE-306) in the engineering and management protocol of Phoenix Contact classic line controllers: anyone who can reach TCP port 1962 on an ILC, AXC 1050/3050 or RFC 4xx can read data, change code and configuration, update firmware or shut the device down. There is no firmware fix. NVD scores it 9.8.
Vulnerability summary
CVSS base score
9.8
Critical severity
EPSS score (FIRST)
3.2%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2019-9201 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| Phoenix Contact ILC 131 ETH, ILC 131 ETH/XC, ILC 151 ETH, ILC 151 ETH/XC, ILC 171 ETH 2TX, ILC 191 ETH 2TX, ILC 191 ME/AN | cpe:2.3:o:phoenixcontact:ilc_151_eth_firmware:-:*:*:*:*:*:*:* | all firmware versions (NVD CPEs, CERT@VDE VDE-2019-015); no fix, mitigations only |
| Phoenix Contact AXC 1050, AXC 1050 XC and AXC 3050 | cpe:2.3:o:phoenixcontact:axc_1050_firmware:-:*:*:*:*:*:*:* | all firmware versions (VDE-2019-015); protocols can be disabled from FW 3.01 (AXC 1050) and FW 5.60 (AXC 3050) |
| Phoenix Contact ILC 1x1 GSM/GPRS and ILC 3xx | — | all firmware versions (VDE-2019-015, CISA ICSA-22-172-05); protocols can be disabled from FW 4.42 (ILC 1x1) and FW 3.98 (ILC 3xx); no NVD CPE |
| Phoenix Contact RFC 460R PN 3TX, RFC 460R PN 3TX-S, RFC 470 PN 3TX, RFC 470S PN 3TX, RFC 480S PN 4TX | — | all firmware versions (VDE-2019-015); protocols can be disabled from FW 4.20 to 6.10 depending on model; no NVD CPE |
| Phoenix Contact RFC 430 ETH-IB, RFC 450 ETH-IB, FC 350 PCI ETH, PC WORX SRT, PC WORX RT BASIC | — | all versions (VDE-2019-015); protocols cannot be disabled, network isolation only; no NVD CPE |
What does this mean for affected devices?
NVD's description: "Multiple Phoenix Contact devices allow remote attackers to establish TCP sessions to port 1962 and obtain sensitive information or make changes, as demonstrated by using the Create Backup feature to traverse all directories." NVD's Primary score is CVSS v3.1 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), the same as MITRE's CNA score, with CWE-306 (missing authentication for critical function). The record was published on 2019-02-26, months before the vendor advisory, and NVD's CPE list is narrower than Phoenix Contact's: it names only the ILC 131, 151, 171 and 191 ETH variants and the AXC 1050 (NVD).
Why does port 1962 have no authentication?
Phoenix Contact says the classic line was designed for closed industrial networks: "The communication protocols used for device management and configuration do not feature authentication measures." CERT@VDE published VDE-2019-015 on 7 August 2019 and Update A on 21 June 2022, which added more controllers and an application note on switching off the unauthenticated ports. Per the advisory, on an unprotected network "an unauthorized attacker can change or download the device code/configuration, start or stop services, update or modify the firmware or shutdown the device". Sergiu Sechel reported it, and the CSAF credits Forescout with re-discovering it (CERT@VDE CSAF). CISA republished it as ICSA-22-172-05 on 21 June 2022 and states that no known public exploits specifically target it.
The same controllers also accept unsigned logic, tracked as CVE-2022-31800, and the ILC 1x0 and 1x1 can be cut off the network with crafted packets, tracked as CVE-2021-33541.
Which controllers can switch the protocol off?
There is no firmware that adds authentication. Where the firmware supports it, the OT protocols can be disabled through the CPU services on the console or the Web-based Management (WBM):
| Controller | Minimum firmware to disable the protocols |
|---|---|
| ILC 1x1, ILC 1x1 GSM/GPRS | FW 4.42 |
| ILC 3xx | FW 3.98 |
| AXC 1050, AXC 1050 XC | FW 3.01, FW 5.00 for WBM |
| AXC 3050 | FW 5.60, FW 6.30 for WBM |
| RFC 470 PN 3TX, RFC 470S PN 3TX | FW 4.20 |
| RFC 460R PN 3TX / 3TX-S | FW 5.00 / FW 5.30 |
| RFC 480S PN 4TX | FW 6.10 |
| ILC 1x0, RFC 430/450 ETH-IB, FC 350 PCI ETH, PC WORX SRT, PC WORX RT BASIC | Not possible |
For the last row the only control is the network: a closed cell, a firewall that allows port 1962 only from the engineering workstation, and VPN for remote access. Our Phoenix Contact PLCnext and classic line security guide sets out the zone design and the PLCnext line, whose firmware fixes include CVE-2020-12519 and CVE-2021-34570.
Is CVE-2019-9201 exploited?
CVE-2019-9201 is not in the CISA KEV catalog as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.03164, the 88th percentile, in the 2026-11-17 dataset (CISA KEV, FIRST EPSS). Because the weakness is missing authentication by design, an attacker who reaches the port needs no exploit code, only the engineering protocol.
Evidence
- NVD: remote attackers establish TCP sessions to port 1962 and obtain sensitive information or make changes; NVD Primary and MITRE CNA CVSS v3.1 9.8 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H; CVSS v2 Primary 9.0; CWE-306; CPEs ILC 131/151 ETH(/XC), ILC 171/191 ETH 2TX, ILC 191 ME/AN, AXC 1050; published 2019-02-26. — NVD
- VDE-2019-015 CSAF: initial release 2019-08-07, Update A 2022-06-21; classic line designed for closed networks, protocols do not feature authentication; impact change/download code and configuration, start/stop services, modify firmware, shut down; all firmware of AXC 1050/1050 XC/3050, FC 350 PCI ETH, ILC1x0, ILC1x1, ILC 1x1 GSM/GPRS, PC WORX RT BASIC/SRT, RFC 430/450/460R/470/470S/480S affected; table of minimum firmware to disable protocols; CVSS 9.8; reported by Sergiu Sechel, re-discovered by Forescout. — CERT@VDE VDE-2019-015 (CSAF)
- ICSA-22-172-05 (2022-06-21): CWE-306, CVSS v3 9.8; ILC 1x0/1x1/3xx, AXC 1050/3050, RFC 4xx, FC 350, PC WORX SRT/RT BASIC; closed networks and firewall; disable OT protocols; no known public exploits specifically target this vulnerability. — CISA CSAF ICSA-22-172-05
- 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.03164, percentile 0.88222, dataset 2026-11-17. — FIRST EPSS

Related advisories
Sources
- NVD
- CERT@VDE VDE-2019-015: Phoenix Contact security advisory for multiple industrial controllers
- CERT@VDE CSAF: VDE-2019-015 (machine-readable advisory)
- CISA ICS Advisory ICSA-22-172-05: Phoenix Contact Classic Line Industrial Controllers
- CISA CSAF: ICSA-22-172-05 (machine-readable advisory)
- CISA KEV
- FIRST EPSS
Frequently asked questions
Is there a firmware update that fixes CVE-2019-9201?
No. Phoenix Contact designed the classic line for closed networks and its management protocol has no authentication. On ILC 1x1 from FW 4.42, ILC 3xx from FW 3.98, AXC 1050 from FW 3.01 and AXC 3050 from FW 5.60 the protocols can be switched off; on ILC 1x0, RFC 430/450 ETH-IB and FC 350 PCI ETH they cannot (per CERT@VDE VDE-2019-015).
What can an attacker do through port 1962?
Per Phoenix Contact, an attacker on an unprotected network can change or download the device code and configuration, start or stop services, update or modify the firmware or shut the device down. NVD adds that the Create Backup feature can be used to traverse all directories (per VDE-2019-015 and NVD).
How do I protect classic line controllers against CVE-2019-9201?
Keep them in a closed network or behind a firewall that allows TCP port 1962 only from named engineering workstations, use VPN for remote access, and disable the OT protocols through CPU services or Web-based Management where the firmware supports it (per VDE-2019-015 and CISA ICSA-22-172-05).
Is CVE-2019-9201 in the CISA KEV catalog?
No, not as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.03164, the 88th percentile, in the 2026-11-17 dataset, the highest of the Phoenix Contact controller CVEs on this site (per CISA KEV and FIRST EPSS).
Questions about this page?