CLICK PLUS C0-0x CPU firmware: Use of a Broken or Risky Cryptographic Algorithm
CVE-2025-59484 is a high-severity use of a broken or risky cryptographic algorithm vulnerability in CLICK PLUS C0-0x CPU firmware from AutomationDirect, with a CVSS 3.1 base score of 8.3 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists version v3.71 as the first without the flaw, so updating CLICK PLUS C0-0x CPU firmware to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.12% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update CLICK PLUS C0-0x CPU firmware to v3.71 or a later version.
- Update CLICK PLUS C0-1x CPU firmware to v3.71 or a later version.
- Update CLICK PLUS C2-x CPU firmware to v3.71 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| AutomationDirect | CLICK PLUS C0-0x CPU firmware | before v3.71 | v3.71 |
| AutomationDirect | CLICK PLUS C0-1x CPU firmware | before v3.71 | v3.71 |
| AutomationDirect | CLICK PLUS C2-x CPU firmware | before v3.71 | v3.71 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- LowPerformance or availability is reduced.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L. Scored by CNA (hq.dhs.gov).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.7 | High | CNA (hq.dhs.gov) |
| CVSS 3.1 | 8.3 | High | CNA (hq.dhs.gov) |
Official description
The use of a broken or risky cryptographic algorithm was discovered in firmware version 3.60 of the Click Plus PLC. The vulnerability relies on the fact that the software uses an insecure implementation of the RSA encryption algorithm.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of a Broken or Risky Cryptographic Algorithm
The product uses a broken or risky cryptographic algorithm or protocol.
How developers prevent this class of flaw
- Ensure that the design allows one cryptographic algorithm to be replaced with another in the next generation or version. Where possible, use wrappers to make the interfaces uniform. This will make it easier to upgrade to stronger algorithms. With hardware, design the product at the Intellectual Property (IP) level so that one cryptographic algorithm can be replaced with another in the next generation of the hardware product.
- Carefully manage and protect cryptographic keys (see CWE-320). If the keys can be guessed or stolen, then the strength of the cryptography itself is irrelevant.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Industry-standard implementations will save development time and may be more likely to avoid errors that can occur during implementation of cryptographic algorithms. Consider the ESAPI Encryption feature.
More Use of a Broken or Risky Cryptographic Algorithm vulnerabilities (CWE-327)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in CLICK PLUS C0-0x CPU firmware
- 8.3 High severity
Recent Use of a Broken or Risky Cryptographic Algorithm vulnerabilities
- 7.2 High severity
- 7.5 High severity
- 7.5 High severity
- 8.1 High severity
- 7.0 High severity
- 9.9 Critical severity
Spotted an error? Tell us.