# CVE-2024-32011: Command injection in Spectrum Power 4

> Attackers can execute arbitrary commands as an administrative user via the network-accessible user interface in Siemens Spectrum Power 4.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Nov 2025
- **Updated:** 12 Nov 2025
- **Also known as:** GHSA-wrgq-x2fx-9ww7

## What is CVE-2024-32011?

CVE-2024-32011 is a high-severity command injection vulnerability in Siemens Spectrum Power 4, published on 11 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability has been identified in Spectrum Power 4 (All versions < V4.70 SP12 Update 2). The affected application is vulnerable to run arbitrary commands via the user interface. This user interface can be used via the network and allows the execution of commands as administrative application user.

Weakness: CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)

## Which versions are affected by CVE-2024-32011?


## How do I fix CVE-2024-32011?

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

## Is CVE-2024-32011 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-32011 and fix it if it is affected.

What it is: CVE-2024-32011 is a high-severity command injection vulnerability in Siemens Spectrum Power 4, published on 11 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-32011 in the wild and no public exploit code.

Affected product: Siemens Spectrum Power 4. 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-2024-32011/ (Markdown: https://insights.sbomify.com/CVE-2024-32011/index.md)
```

## Sources

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

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