Skip to content
Fencer Intel
high 7.5

CVE-2016-5744 json

Siemens SIMATIC WinCC 7.0 through SP3 and 7.2 allows remote attackers to read arbitrary WinCC station files via crafted packets.

published 2016-07-22 10 y ago modified 2026-06-17 4 mo ago also EUVD-2016-6679

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

Summary

Siemens SIMATIC WinCC 7.0 through SP3 and 7.2 allows remote attackers to read arbitrary WinCC station files via crafted packets.

Vendor advisories

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

cisa ICSA-16-208-01C updated cvss 7.5

Siemens SIMATIC WinCC, PCS 7, and WinCC Runtime Professional Vulnerabilities (Update C)

  • Siemens SIMATIC PCS 7 (WinCC, Batch, Route Control, OPEN PCS 7) <V7.1_SP4_with_WinCC_V7.0_SP2_Update_12, <V8.0_SP2_with_WinCC_V7.2_Update_13, <8.1_SP1_with_WinCC_V7.3_Update_10, <8.2_with_WinCC_V7.4_Update_1 Siemens SIMATIC WinCC 7.0 SP2 <Update_12 Siemens SIMATIC WinCC 7.0 SP3 <Update_8 Siemens SIMATIC WinCC 7.2 <Update_13 Siemens SIMATIC WinCC 7.3 <Update_10 Siemens SIMATIC WinCC 7.4 <Update_1
    +1 more products
    Siemens SIMATIC WinCC Runtime Professional <V13_SP_1_Update_9
    affected: mitigation “SIMATIC WinCC V7.0 SP3:: Update to V7.0 SP3 Update 8 (https://support.industry.siemens.com/cs/ww/en/view/109741127)” support.industry.siemens.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

Exploit prediction

4.40% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel 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.