# CVE-2024-25136: AutomationDirect C-MORE EA9 HMI Path Traversal

> An attacker can exploit a path traversal vulnerability in AutomationDirect C-MORE EA9 HMI to access unauthorized files via unsanitized URL inputs.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Mar 2024
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-rv26-9qp5-5mh3

## What is CVE-2024-25136?

CVE-2024-25136 is a high-severity path traversal vulnerability in AutomationDirect C-MORE EA9 HMI EA0-T7CL-R, published on 26 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2024-25136?


## How do I fix CVE-2024-25136?

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

## Is CVE-2024-25136 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-25136 and fix it if it is affected.

What it is: CVE-2024-25136 is a high-severity path traversal vulnerability in AutomationDirect C-MORE EA9 HMI EA0-T7CL-R, published on 26 Mar 2024. 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-2024-25136 in the wild and no public exploit code.

Affected product: AutomationDirect C-MORE EA9 HMI EA0-T7CL-R. 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-2024-25136/ (Markdown: https://insights.sbomify.com/CVE-2024-25136/index.md)
```

## Sources

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

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