Skip to content
Fencer Intel
medium 6.1

CVE-2025-67652 json

AutomationDirect CLICK Programmable Logic Controller Weak Encoding for Password

published 9mo ago modified 4mo ago also EUVD-2026-4502

cvss
6.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 1%
public exploits
0
none known

Summary

An attacker with access to the project file could use the exposed credentials to impersonate users, escalate privileges, or gain unauthorized access to systems and services. The absence of robust encryption or secure handling mechanisms increases the likelihood of this type of exploitation, leaving sensitive information more vulnerable.

Patch / fix

  • AutomationDirect CLICK Programmable Logic Controller V3.90

Is CVE-2025-67652 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

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

cisa ICSA-26-022-02 updated cvss 6.1

AutomationDirect CLICK Programmable Logic Controller

  • AutomationDirect CLICK Programmable Logic Controller C0-0x, C0-1x, C2-x
    affected: mitigation “AutomationDirect recommends that users update CLICK PLUS and firmware to V3.90.” automationdirect.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

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
9mo ago

Exploit prediction

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

CVSS scores

assigned by version score vector
CNA 3.1 6.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

Affected products

  • AutomationDirect CLICK Programmable Logic Controller

Classification

Weakness
  • CWE-261 Weak Encoding for Password

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.