# CVE-2025-54926: Path traversal in EcoStruxure™ Power Monitoring Expert (PME)

> An authenticated admin can achieve remote code execution via path traversal in file uploads on Schneider Electric power monitoring software.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Aug 2025
- **Updated:** 20 Aug 2025
- **Also known as:** GHSA-9q86-673r-39p8

## What is CVE-2025-54926?

CVE-2025-54926 is a high-severity path traversal vulnerability in Schneider Electric EcoStruxure™ Power Monitoring Expert (PME), published on 20 Aug 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability exists that could cause remote code execution when an authenticated attacker with admin privileges uploads a malicious file over HTTP which then gets executed.

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

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


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

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

## Is CVE-2025-54926 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-54926 is a high-severity path traversal vulnerability in Schneider Electric EcoStruxure™ Power Monitoring Expert (PME), published on 20 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-54926 in the wild and no public exploit code.

Affected product: Schneider Electric EcoStruxure™ Power Monitoring Expert (PME). 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-54926/ (Markdown: https://insights.sbomify.com/CVE-2025-54926/index.md)
```

## Sources

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

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