Insufficient Verification of Data Vulnerability in ProConOS/ProConOS eCLR SDK and MULTIPROG Engineering tool

published 2022-06-21 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-53190

cvss: 9.8; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 1.1%; EPSS 1.1% chance of exploitation in 30 days, percentile 66%
public exploits: 0; none known

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

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-22-172-04 updated 2022-06-21 cvss 9.8

Phoenix Contact ProConOS and MULTIPROG

Phoenix Contact MULTIPROG Phoenix Contact ProConoS Phoenix Contact ProConoS eCLR
affected: mitigation “Manufacturers using ProConOS/ProConOS eCLR in automation devices are advised to check implementation and publish an advisory according to their product.” dam-mdc.phoenixcontact.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: total
Assessed: 5 mo ago (2026-06-02)

Exploit prediction

1.14% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	10.0	AV:N/AC:L/Au:N/C:C/I:C/A:C

Affected products

PHOENIX CONTACT MULTIPROG
PHOENIX CONTACT ProConOS
PHOENIX CONTACT ProConOS eCLR

Classification

Weakness

CWE-345 Insufficient Verification of Data Authenticity

References

cert.vde.com /en/advisories/VDE-2022-026/
mitigation, third-party-advisory

Sources

CVE List CVE-2022-31801
NVD CVE-2022-31801

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary