Skip to content
Fencer Intel
high 7.3

CVE-2016-8366 json

Webvisit in Phoenix Contact ILC PLCs offers a password macro to protect HMI pages on the PLC against casual or coincidental opening of HMI…

published 2018-04-05 8 y ago modified 2026-06-17 4 mo ago also EUVD-2016-9214

cvss
7.3
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
5.7%
EPSS 5.7% chance of exploitation in 30 days, percentile 93%
public exploits
1
Exploit-DB

Summary

Webvisit in Phoenix Contact ILC PLCs offers a password macro to protect HMI pages on the PLC against casual or coincidental opening of HMI pages by the user. The password macro can be configured in a way that the password is stored and transferred in clear text.

Vendor advisories

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

cisa ICSA-16-313-01 updated cvss 7.3

Phoenix Contact ILC PLC Authentication Vulnerabilities

  • Phoenix Contact ILC 1xx PLCs
    affected: mitigation “For more information on this vulnerability and the associated update and mitigation strategies, please email Phoenix Contact at the following address: (mailto:automation-service@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

Timeline

  1. Published
  2. First public exploit (EDB-45586)

Exploit prediction

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

Exploits and checks

  • EDB-45586 Phoenix Contact WebVisit 6.40.00 - Password Disclosure webapps, 2018-10-11

CVSS scores

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

Affected products

  • Phoenix Contact Phoenix Contact ILC PLCs

Classification

Weakness
  • CWE-312 Cleartext Storage of Sensitive Information
  • CWE-255 Credentials Management Errors

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.