# CVE-2025-50121: Command injection in EcoStruxure™ IT Data Center Expert

> Unauthenticated attackers can execute arbitrary code via OS command injection if the HTTP interface is enabled.

- **Severity:** Critical 9.5 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:L/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2025
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-4gh4-j9hh-74h5

## What is CVE-2025-50121?

CVE-2025-50121 is a critical command injection vulnerability in Schneider Electric EcoStruxure™ IT Data Center Expert, published on 11 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
vulnerability exists that could cause unauthenticated remote code execution when a malicious folder is created
over the web interface HTTP when enabled. HTTP is disabled by default.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2025-50121 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-50121 is a critical command injection vulnerability in Schneider Electric EcoStruxure™ IT Data Center Expert, published on 11 Jul 2025. 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-2025-50121 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-50121/ (Markdown: https://insights.sbomify.com/CVE-2025-50121/index.md)
```

## Sources

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

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