# CVE-2025-5296: Path traversal in SESU

> A low-privileged attacker can exploit improper link resolution to write arbitrary data to protected locations, leading to privilege escalation or file corruption.

- **Severity:** High 7.0 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2025
- **Updated:** 18 Aug 2025
- **Also known as:** GHSA-8wcv-4h46-66mg

## What is CVE-2025-5296?

CVE-2025-5296 is a high-severity path traversal vulnerability in Schneider Electric SESU, published on 18 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

CWE-59: Improper Link Resolution Before File Access ('Link Following') vulnerability exists that could cause 
arbitrary data to be written to protected locations, potentially leading to escalation of privilege, arbitrary file 
corruption, exposure of application and system information or persistent denial of service when a low-privileged 
attacker tampers with the installation folder.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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


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

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

## Is CVE-2025-5296 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-5296 is a high-severity path traversal vulnerability in Schneider Electric SESU, published on 18 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-5296 in the wild and no public exploit code.

Affected product: Schneider Electric SESU. 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-5296/ (Markdown: https://insights.sbomify.com/CVE-2025-5296/index.md)
```

## Sources

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

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