CVE-2025-0960
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAutomationDirect C-more EA9 HMI contains a function with bounds checks that can be skipped, which could result in an attacker abusing the function to cause a denial-of-service condition or achieving remote code execution on the affected device.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe AutomationDirect C-more EA9 HMI contains a vulnerability where bounds checks in a specific function can be bypassed, allowing an attacker to trigger a denial-of-service condition or achieve remote code execution on the affected device.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm the device is a C-more EA9 HMILog into the HMI or check the device documentation/model label to verify the exact model number is AutomationDirect C-more EA9 seriesAffected if The device is not an AutomationDirect C-more EA9 HMI model
-
Identify the installed firmware versionAccess the HMI web interface, use the EA9 programming software, or check the device system information screen to retrieve the firmware version numberAffected if The firmware version cannot be determined or is older than the vendor-patched version (compare against official AutomationDirect release notes)
-
Assess network exposure of the HMIReview network firewall rules and VLAN configuration to determine if the HMI is directly accessible from untrusted networks or the internetAffected if The HMI has direct accessibility from external networks without firewall protection
-
Check for unexpected service behavior or crashesReview system logs, event logs, or any available diagnostic information on the HMI for unexpected reboots, service failures, or error messages related to memory operationsAffected if The HMI exhibits unexplained crashes, restarts, or error messages indicating memory corruption
You are affected if you have an AutomationDirect C-more EA9 HMI running firmware that predates the vendor fix, particularly if the device is network-accessible from untrusted segments.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor-provided firmware updates when available; until then, isolate the HMI from untrusted networks and implement compensating controls such as network segmentation and access restrictions.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0960 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-0960 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data