CVE-2016-8371

highpriority · track · 43EPSS 0.109 · 96 %ileexploit · PoCEUUS
grimoire priorityP1 · Urgent
Exploitable?
Public exploit
1 exploit · PoC
Likely / severe?
10.9% (96th) EPSS
CVSS 7.5 · high
Is it mine?
4 products
Check your exposure
Who says so?
4 sources
cnnvd · enisa_euvd · cisa_csaf_ot · nvd

EPSS · scored 2026-10-27

The web server in Phoenix Contact ILC PLCs can be accessed without authenticating even if the authentication mechanism is enabled.

01

remediations

Vendor fix, mitigation, or workaround guidance, as published by each source.

No vendor fix yet; a mitigation is available.

  • MitigationILC 1xx PLCscisa_csaf_ot

    Connecting devices to a network via Ethernet always entails the risk of unauthorized access to the network. Phoenix Contact recommends that users implement an adequate defense–in-depth networking architecture (including the following) for control systems where these devices are operating: Devices should not be exposed to public networks without the use of virtual private networks (VPNs) for remote access. Firewalls should be used for network segmentation or controller isolation. Available communication channels or ports not needed in the application should be turned off. Administrators and users should check whether the application offers any option of deactivating active communication channels (e.g., SNMP, FTP, BootP, DCP), or setting passwords to prevent third parties from unauthorized accessing the controller and modifying the system. Access to the devices should be limited to the fewest possible authorized personnel. Change standard or default passwords when first installing every component. Passwords should be changed in regular interval in order to reduce risks of becoming public. Passwords should have a maximum strength by the use of small and capital letters as well as numbers and special characters with a length of at least 10 characters. Conduct regular thread analyses to discover whether current measures meet the safety requirements. Install and maintain security software in order to defend new or recurring risks

02

cvss

Technical severity, 0–10. One row per scoring source.

7.5
010

base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 6.7–7.5

v2.07.5highAV:N/AC:L/Au:N/C:P/I:P/A:Pprimary · NVD / NIST USexploitability 10 · impact 6.4
v3.07.3highCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:Lprimary · NVD / NIST USexploitability 3.9 · impact 3.4
v3.07.3highCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:Lsecondary · CISA US
v3.06.7mediumCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:Usecondary · CVSS-BT (t0sche)
03

weaknesses

The CWE weakness classes this flaw belongs to.

04

exploits (1)

Public proof-of-concept and weaponised exploit code.

05

affected products (4)

Products and version ranges known to be affected.

06

advisories (1)

Vendor and ecosystem advisories describing this.

  • ICSA-16-313-01Phoenix Contact ILC PLC Authentication Vulnerabilities2016-08-12icsa · cisa_csaf_otUS

    This CSAF advisory was extracted from unstructured data and may contain inaccuracies. If you notice any errors, please reach out to the designated contact at CISA CSAF: central@cisa.dhs.gov

07

also known as (3)

Other names and identifiers for this entity.

08

sources

Which sources assert this record, and when.

published 2018-04-05modified 2026-06-17
10

references (9)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan