Skip to main content
No exploitation reportedFix available

CVE-2020-12497

No exploitation reported by the sources we read.

  • Published2020-07-01
  • Fixed in1.87
  • WeaknessCWE-121 · CWE-787

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2020-07-0116:15CVE publishedNVD
  2. 2026-10-2319:23EPSS crossed 10 %FIRST EPSS

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2020-12497?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2020-12497?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Phoenixcontact pc worx
BranchAffectedFixed in
1.87< 1.871.87
Phoenixcontact pc worx express
BranchAffectedFixed in
1.87≤ 1.87no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • ICSA-20-191-01 CISA2 known affected

    Phoenix Contact Automation Worx Software Suite

    PC Worx Express: version 1.87 and prior · PC Worx: version 1.87 and prior

Full record on NVD

Fix

  1. Update Phoenixcontact pc worx to 1.87
  2. Mitigation from the vendor CISA ICSA-20-191-01 · 2 productsPhoenix Contact recommends users exchange project files only using secure file exchange services. Project files should not be exchanged via unencrypted email. In addition, we recommend exchanging or storing project files together with a checksum to ensure their integrity.
  3. Mitigation from the vendor CISA ICSA-20-191-01 · 2 productsWith the next version of Automation Worx Software Suite, a sharpened input data validation, with respect to buffer size and description of size and number of objects referenced in a file, will be implemented.

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • CNACVSS 3.17.8read 2026-10-23
  • NVDCVSS 3.17.8read 2026-10-23
  • NVDCVSS 2.06.8read 2026-10-23
  • CNAweakness (CWE)CWE-121read 2026-10-23
  • NVDweakness (CWE)CWE-787read 2026-10-23
  • FIRST EPSSEPSS score14.7 %read 2026-10-23

Technical details

CVSS v3 Vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Published
2020-07-01
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2020-12497?

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.

Is CVE-2020-12497 actively exploited?

Active exploitation of CVE-2020-12497 has not been confirmed. Its EPSS score was 14.7% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2020-12497?

CVE-2020-12497 has a CVSS v3 base score of 7.8 (HIGH severity), with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month