# CVE-2025-58069: AutomationDirect CLICK PLUS Use of Hard-coded Cryptographic Key

> Attackers can exploit a hard-coded AES key in AutomationDirect CLICK PLUS PLC firmware to bypass security protections on initial session messages.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2025
- **Updated:** 24 Sep 2025
- **Also known as:** GHSA-wgx5-63fm-m4g7

## What is CVE-2025-58069?

CVE-2025-58069 is a medium-severity vulnerability in AutomationDirect CLICK PLUS C0-0x CPU firmware, published on 23 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The use of a hard-coded cryptographic key was discovered in firmware version 3.60 of the Click Plus PLC. The vulnerability relies on the fact that the software contains a hard-coded AES key used to protect the initial messages of a new KOPS session.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

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


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

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

## Is CVE-2025-58069 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-58069 is a medium-severity vulnerability in AutomationDirect CLICK PLUS C0-0x CPU firmware, published on 23 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-58069 in the wild and no public exploit code.

Affected product: AutomationDirect CLICK PLUS C0-0x CPU firmware. 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-58069/ (Markdown: https://insights.sbomify.com/CVE-2025-58069/index.md)
```

## Sources

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

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