# CVE-2025-58473: AutomationDirect CLICK PLUS Improper Resource Shutdown or Release

> Unauthenticated attackers can cause denial of service by exhausting device sessions in AutomationDirect CLICK PLUS PLCs.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/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-jpgr-mp9r-3h9m

## What is CVE-2025-58473?

CVE-2025-58473 is a high-severity denial of service 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

An improper resource shutdown or release vulnerability has been identified in the Click Plus C2-03CPU-2 device running firmware version 3.60. The vulnerability allows an unauthenticated attacker to perform a denial-of-service attack by exhausting all available device sessions of the Click Programming Software.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

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


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

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

## Is CVE-2025-58473 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-58473 is a high-severity denial of service 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-58473 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-58473/ (Markdown: https://insights.sbomify.com/CVE-2025-58473/index.md)
```

## Sources

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

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