CVE-2016-8371 in the critical feed json
The web server in Phoenix Contact ILC PLCs can be accessed without authenticating even if the authentication mechanism is enabled.
published 2018-04-05 8 y ago modified 2026-06-17 4 mo ago also EUVD-2016-9219
- cvss
- 7.3
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 10.9%
- EPSS 10.9% chance of exploitation in 30 days, percentile 95%
- public exploits
- 1
- Exploit-DB
Summary
The web server in Phoenix Contact ILC PLCs can be accessed without authenticating even if the authentication mechanism is enabled.
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 PLCsaffected: 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
- Published
- First public exploit (EDB-45590)
Exploit prediction
10.85% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-45590 Phoenix Contact WebVisit 2985725 - Authentication Bypass webapps, 2018-10-12
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 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- Phoenix Contact Phoenix Contact ILC PLCs
Classification
References
-
exploit-db.com
/exploits/45590/
exploit
-
ics-cert.us-cert.gov
/advisories/ICSA-313-01
third-party-advisory, us-government-resource
-
securityfocus.com
/bid/94163
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2016-8371
- NVD CVE-2016-8371
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.