CVE-2020-12497 in the critical feed json
Phoenix Contact Automation Worx <= 1.87: stack-based overflow
published 2020-07-01 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-4799
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 14.7%
- EPSS 14.7% chance of exploitation in 30 days, percentile 96%
- public exploits
- 0
- none known
Summary
PLCopen XML file parsing in Phoenix Contact PC Worx and PC Worx Express version 1.87 and earlier can lead to a stack-based overflow. Manipulated PC Worx projects could lead to a remote code execution due to insufficient input data validation.
Patch / fix
- phoenixcontact pc_worx 1.87
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-20-191-01 updated cvss 7.8
Phoenix Contact Automation Worx Software Suite
-
Phoenix Contact PC Worx <= 1.87 Phoenix Contact PC Worx Express <= 1.87affected: mitigation
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
14.67% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/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 |
Affected products
- Phoenix Contact Automation Worx
- Phoenix Contact Automation Worx Express
Classification
References
-
cert.vde.com
/de-de/advisories/vde-2020-023
vendor-advisory
-
zerodayinitiative.com
/advisories/ZDI-20-825/
third-party-advisory, vdb-entry
-
zerodayinitiative.com
/advisories/ZDI-21-398/
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2020-12497
- NVD CVE-2020-12497
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.