# CVE-2025-67652: AutomationDirect CLICK Programmable Logic Controller Weak Encoding for Password

> Weak password encoding in AutomationDirect CLICK PLCs allows attackers with project file access to impersonate users and escalate privileges.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jan 2026
- **Updated:** 23 Jan 2026
- **Also known as:** GHSA-cf6r-jpjw-rvwr

## What is CVE-2025-67652?

CVE-2025-67652 is a medium-severity vulnerability in AutomationDirect CLICK Programmable Logic Controller, published on 22 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-261 (Weak Encoding for Password)

## Which versions are affected by CVE-2025-67652?


## How do I fix CVE-2025-67652?

No fix has been published for CVE-2025-67652 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-67652 being exploited?

There is no known exploitation of CVE-2025-67652 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-67652 and fix it if it is affected.

What it is: CVE-2025-67652 is a medium-severity vulnerability in AutomationDirect CLICK Programmable Logic Controller, published on 22 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-67652 in the wild and no public exploit code.

Affected product: AutomationDirect CLICK Programmable Logic Controller. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-67652/ (Markdown: https://insights.sbomify.com/CVE-2025-67652/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-67652
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-67652
- OSV: https://osv.dev/vulnerability/CVE-2025-67652

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-67652/
Summaries are generated and may contain mistakes; the official description above is the record.