# CVE-2025-40949: Command injection in RUGGEDCOM ROX MX5000

> Authenticated attackers can inject commands into the Web UI scheduler to execute arbitrary code with root privileges on RUGGEDCOM ROX devices.

- **Severity:** High 8.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2026
- **Updated:** 13 May 2026
- **Also known as:** GHSA-pfwq-586r-qjjm

## What is CVE-2025-40949?

CVE-2025-40949 is a high-severity command injection vulnerability in Siemens RUGGEDCOM ROX MX5000, published on 12 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability has been identified in RUGGEDCOM ROX MX5000 (All versions < V2.17.1), RUGGEDCOM ROX MX5000RE (All versions < V2.17.1), RUGGEDCOM ROX RX1400 (All versions < V2.17.1), RUGGEDCOM ROX RX1500 (All versions < V2.17.1), RUGGEDCOM ROX RX1501 (All versions < V2.17.1), RUGGEDCOM ROX RX1510 (All versions < V2.17.1), RUGGEDCOM ROX RX1511 (All versions < V2.17.1), RUGGEDCOM ROX RX1512 (All versions < V2.17.1), RUGGEDCOM ROX RX1524 (All versions < V2.17.1), RUGGEDCOM ROX RX1536 (All versions < V2.17.1), RUGGEDCOM ROX RX5000 (All versions < V2.17.1). Affected devices do not properly sanitize user-supplied input in the Scheduler functionality of the Web UI, allowing commands to be injected into the task scheduling backend.

This could allow an authenticated remote attacker to execute arbitrary commands with root privileges on the underlying operating system.

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

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

It affects 11 products.


Products: Siemens Ruggedcom Rox Mx5000 Firmware, Siemens Ruggedcom Rox Mx5000re Firmware, Siemens Ruggedcom Rox Rx1400 Firmware, Siemens Ruggedcom Rox Rx1500 Firmware, Siemens Ruggedcom Rox Rx1501 Firmware, Siemens Ruggedcom Rox Rx1510 Firmware, Siemens Ruggedcom Rox Rx1511 Firmware, Siemens Ruggedcom Rox Rx1512 Firmware, Siemens Ruggedcom Rox Rx1524 Firmware, Siemens Ruggedcom Rox Rx1536 Firmware, Siemens Ruggedcom Rox Rx5000 Firmware.

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

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

## Is CVE-2025-40949 being exploited?

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

## Other vulnerabilities in Siemens RUGGEDCOM ROX MX5000

- [CVE-2023-36750](https://insights.sbomify.com/CVE-2023-36750/): Command injection in RUGGEDCOM ROX MX5000 (critical 9.1)
- [CVE-2023-36751](https://insights.sbomify.com/CVE-2023-36751/): Command injection in RUGGEDCOM ROX MX5000 (critical 9.1)
- [CVE-2023-36752](https://insights.sbomify.com/CVE-2023-36752/): Command injection in RUGGEDCOM ROX MX5000 (critical 9.1)
- [CVE-2023-36753](https://insights.sbomify.com/CVE-2023-36753/): Command injection in RUGGEDCOM ROX MX5000 (critical 9.1)
- [CVE-2023-36754](https://insights.sbomify.com/CVE-2023-36754/): Command injection in RUGGEDCOM ROX MX5000 (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-40949 is a high-severity command injection vulnerability in Siemens RUGGEDCOM ROX MX5000, published on 12 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-40949 in the wild and no public exploit code.

Affected product: Siemens RUGGEDCOM ROX MX5000. 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-40949/ (Markdown: https://insights.sbomify.com/CVE-2025-40949/index.md)
```

## Sources

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

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