dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-25136

HIGH · 7.5 CVSS v3.1 Published 2024-03-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
There is a function in AutomationDirect C-MORE EA9 HMI that allows an attacker to send a relative path in the URL without proper sanitizing of the content.

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 confidence

A path traversal vulnerability exists in the AutomationDirect C-MORE EA9 HMI web interface. The application fails to properly sanitize relative path sequences in URL parameters, allowing attackers to access files outside the web root directory via sequences like '../'. This could enable unauthorized access to sensitive system files, configuration data, or other resources on the HMI device.

MitigationImplement strict input validation and path canonicalization on the server side to reject path traversal characters and sequences. Additionally, ensure the web server runs with minimal file system permissions and apply any vendor-supplied security patches or firmware updates for the C-MORE EA9 HMI.

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the C-MORE EA9 HMI device
    Access the web interface and look for product identification strings in the login page, header, or footer (such as 'C-MORE EA9' or 'AutomationDirect'). Check the page source or HTTP headers for server identification.
    Affected if The device is an AutomationDirect C-MORE EA9 HMI with an accessible web interface.
  2. Confirm the web server is running
    Attempt to access the HTTP service on the device (typically port 80 or 443). A successful connection returning an HMI login page or web interface indicates the web server is active.
    Affected if The web interface is accessible and responding to HTTP/HTTPS requests.
  3. Determine the firmware version
    Log into the HMI web interface and navigate to System Settings or About pages. Alternatively, check any firmware version displayed on the login page footer or within the administration section. Compare the version number against any known affected version ranges for this CVE.
    Affected if The installed firmware version falls within the affected range for CVE-2024-25136 (if vendor publishes specific versions).
  4. Inspect web server configuration for path handling
    If administrative access is available, review the web server configuration files or settings within the C-MORE HMI management interface for path validation or canonicalization settings.
    Affected if The web server lacks proper input validation for URL path parameters or does not reject path traversal sequences.
  5. Test for path traversal vulnerability (cautious probe)
    Using a controlled request, attempt to access a known file outside the web root using '../' sequences in a URL parameter (e.g., request a configuration file path). Observe whether the application returns file contents or an error indicating traversal was blocked. Perform only in authorized, non-production environments.
    Affected if The application returns file contents from outside the intended web root directory, indicating the path traversal vulnerability is present and exploitable.

The environment is affected if the device is an AutomationDirect C-MORE EA9 HMI with an accessible web interface and the installed firmware version matches the affected range for CVE-2024-25136, or if the path traversal test reveals unauthorized file access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and path canonicalization on the server side to reject path traversal characters and sequences. Additionally, ensure the web server runs with minimal file system permissions and apply any vendor-supplied security patches or firmware updates for the C-MORE EA9 HMI.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-25136 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-25136 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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