# CVE-2025-48394: Path traversal in G4 PDU

> Privileged attackers can modify non-sensitive files via path traversal in the CLI limited shell of Eaton G4 PDUs.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2025
- **Updated:** 6 Aug 2025
- **Also known as:** GHSA-wq3p-gjxr-cphp

## What is CVE-2025-48394?

CVE-2025-48394 is a medium-severity path traversal vulnerability in Eaton G4 PDU, published on 6 Aug 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An attacker with authenticated and privileged access could modify the contents of a non-sensitive file by traversing the path in the limited shell of the CLI. This security issue has been fixed in the latest version which is available on the Eaton download center.

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

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


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

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

## Is CVE-2025-48394 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-48394 is a medium-severity path traversal vulnerability in Eaton G4 PDU, published on 6 Aug 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-48394 in the wild and no public exploit code.

Affected product: Eaton G4 PDU. 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-48394/ (Markdown: https://insights.sbomify.com/CVE-2025-48394/index.md)
```

## Sources

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

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