Skip to content
Fencer Vulns
high 8.8

CVE-2019-12869 json

An issue was discovered in PHOENIX CONTACT PC Worx through 1.86, PC Worx Express through 1.86, and Config+ through 1.86.

published 2019-06-24 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-4448

cvss
8.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.8%
EPSS 3.8% chance of exploitation in 30 days, percentile 89%
public exploits
0
none known

Summary

An issue was discovered in PHOENIX CONTACT PC Worx through 1.86, PC Worx Express through 1.86, and Config+ through 1.86. A manipulated PC Worx or Config+ project file could lead to an Out-Of-Bounds Read, Information Disclosure, and remote code execution. The attacker needs to get access to an original PC Worx or Config+ project file to be able to manipulate it. After manipulation, the attacker needs to exchange the original file with the manipulated one on the application programming workstation.

Vendor advisories

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

cisa ICSA-19-171-01 updated cvss 3.3

PHOENIX CONTACT Automation Worx Software Suite

  • Phoenix Contact Config+ Automation Worx Software Suite <= 1.86 Phoenix Contact PC Worx Automation Worx Software Suite <= 1.86 Phoenix Contact PC Worx Express Automation Worx Software Suite <= 1.86
    affected: mitigation “Phoenix Contact is currently working on the next version of the Automation Worx Software Suite. This advisory will be updated with details of the new version when it becomes available.” us-cert.gov

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

Exploit prediction

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

CVSS scores

assigned by version score vector
NVD 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Classification

Weakness

References

Sources

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.