CVE-2025-67652VulnerabilityPublished 22 Jan 2026

CVE-2025-67652: AutomationDirect CLICK Programmable Logic Controller · CWE-261

Affects AutomationDirect CLICK Programmable Logic ControllerSource CVE Database V5

Not known to be exploited · CVSS 6.1 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
AutomationDirectCLICK Programmable Logic Controller	Affected =C0-0x =C0-1x =C2-x	Fixed in–

AI-suggested

European organizations should implement strict access controls and permissions on project files associated with AutomationDirect CLICK PLCs, ensuring only authorized personnel can access or modify them. Encrypting project files at rest and in transit is critical to prevent unauthorized disclosure of embedded credentials. Organizations should enforce network segmentation between IT and OT environments to limit the exposure of PLC configuration files. Regular audits and monitoring of file access logs can help detect unauthorized attempts to access or copy project files. Employing endpoint security solutions on workstations used to handle PLC project files can reduce the risk of insider threats or malware-based theft. Where possible, organizations should request or develop secure handling procedures from AutomationDirect, including secure storage and transmission of project files. Until patches or updates are available, consider implementing multi-factor authentication and additional verification mechanisms for access to PLC management interfaces. Training staff on the sensitivity of project files and the risks of credential exposure is also recommended. Finally, maintain an incident response plan tailored to OT environments to quickly address any detected compromise.

Description

CVE-2025-67652 is a medium severity vulnerability affecting AutomationDirect CLICK Programmable Logic Controllers (PLCs), specifically versions C0-0x, C0-1x, and C2-x. The vulnerability arises from improper handling of credentials within project files, allowing an attacker with access to these files to impersonate users, escalate privileges, or gain unauthorized access to connected systems. Exploitation requires local access to the project file and low complexity attack conditions, with no user interaction needed. The vulnerability impacts confidentiality significantly but has limited effect on integrity and no impact on availability. No public exploits are currently known. European organizations using these PLCs in industrial control environments could face risks of unauthorized access and potential lateral movement within their networks. Mitigation requires strict access controls on project files, encryption of sensitive data, and monitoring for unauthorized access. Countries with significant industrial automation sectors and AutomationDirect market presence, such as Germany, France, Italy, and the UK, are most likely to be affected.

Impact

For European organizations, especially those in manufacturing, energy, and critical infrastructure sectors relying on AutomationDirect CLICK PLCs, this vulnerability presents a risk of unauthorized access to sensitive control systems. The exposure of credentials can lead to impersonation of authorized users and privilege escalation, potentially allowing attackers to move laterally within industrial networks. Although the vulnerability does not directly impact system availability or cause immediate operational disruption, the confidentiality breach could facilitate further attacks, including sabotage or espionage. Given the increasing integration of industrial control systems with corporate IT networks in Europe, exploitation could compromise both operational technology (OT) and information technology (IT) environments. The impact is particularly relevant for organizations with insufficient access controls on project files or inadequate network segmentation between IT and OT. The absence of robust encryption in project files increases the risk of credential theft if files are improperly stored or transmitted. This vulnerability could also affect supply chain security if project files are shared externally without adequate protection.

CWE-261Weak Encoding for Password (opens in a new tab)
Base weaknessOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
Obscuring a password with a trivial encoding does not protect the password.
Passwords should be encrypted with keys that are at least 128 bits in length for adequate security.
OWASP Cheat Sheets
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
HSTS (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (opens in a new tab)
Attack patterns
Rainbow Table Password Cracking (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Jan 2026, 10:00 UTC

WeaknessesCWE-261

Technical details

References

Community reviews

Related threats