# CVE-2025-50124: Privilege escalation in EcoStruxure™ IT Data Center Expert

> A privilege escalation vulnerability in Schneider Electric EcoStruxure IT Data Center Expert allows attackers to gain elevated privileges via a setup script.

- **Severity:** High 7.2 (`CVSS:4.0/AV:P/AC:H/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:L/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2025
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-x2h5-r7cj-6jqv

## What is CVE-2025-50124?

CVE-2025-50124 is a high-severity vulnerability in Schneider Electric EcoStruxure™ IT Data Center Expert, published on 11 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A

CWE-269: Improper Privilege Management vulnerability exists that could cause privilege escalation when the
server is accessed by a privileged account via a console and through exploitation of a setup script.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2025-50124 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-50124 is a high-severity vulnerability in Schneider Electric EcoStruxure™ IT Data Center Expert, published on 11 Jul 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-50124 in the wild and no public exploit code.

Affected product: Schneider Electric EcoStruxure™ IT Data Center Expert. 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-50124/ (Markdown: https://insights.sbomify.com/CVE-2025-50124/index.md)
```

## Sources

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

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