dbcve.org
Ruggedcom Rox Mx5000 FirmwareOperating system · Siemens

CVE-2025-40947

HIGH · 7.5 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 2.17.1 or later.
See remediation →
81/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 during the feature key installation process. This could allow an authenticated remote attacker to inject arbitrary commands, resulting in remote code execution with root privileges on the underlying operating system.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Command injection vulnerability in RUGGEDCOM ROX network devices (MX5000, MX5000RE, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512, RX1524, RX1536, RX5000) allows authenticated attackers to inject arbitrary OS commands through unsanitized user input during the feature key installation process, achieving root-level remote code execution.

MitigationUpgrade all affected devices to RUGGEDCOM ROX V2.17.1 or later. Limit administrative access to trusted personnel only and monitor for suspicious feature key installation activity until patching is complete.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ruggedcom Rox Mx5000 FirmwareOperating system
Affected:< 2.17.1
Ruggedcom Rox Mx5000re FirmwareOperating system
Affected:< 2.17.1
Ruggedcom Rox Rx1400 FirmwareOperating system
Affected:< 2.17.1
Ruggedcom Rox Rx1500 FirmwareOperating system
Affected:< 2.17.1
Ruggedcom Rox Rx1501 FirmwareOperating system
Affected:< 2.17.1
Ruggedcom Rox Rx1510 FirmwareOperating system
Affected:< 2.17.1
Ruggedcom Rox Rx1511 FirmwareOperating system
Affected:< 2.17.1
Ruggedcom Rox Rx1512 FirmwareOperating system
Affected:< 2.17.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model and firmware version
    Access the device CLI or web interface and locate the firmware version information, typically found under System Information, Device Status, or About sections. Compare the installed version against the affected range (all versions below 2.17.1).
    Affected if The device is one of the listed models (MX5000, MX5000RE, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512, RX1524, RX1536, RX5000) and the firmware version is below 2.17.1.
  2. Verify administrative access is enabled
    Check if the web-based management interface or CLI administrative access is enabled on the device. This is typically configurable under System Settings, Network Services, or Access Control menus.
    Affected if Administrative access (web UI or CLI) is enabled and accessible, allowing authenticated users to reach the feature key installation functionality.
  3. Confirm feature key installation functionality presence
    Determine if the device has feature key installation capability available. This is commonly used to enable optional software features in industrial network devices.
    Affected if The device supports feature key installation and this functionality is accessible to authenticated administrators.
  4. Review administrative user accounts
    Audit the list of configured administrative accounts on the device to determine how many users have privileged access. Check if default or weak credentials may be in use.
    Affected if There are administrative accounts configured that could be compromised, allowing an attacker to authenticate and trigger the vulnerable feature key installation process.

A user is affected if they are running any of the listed RUGGEDCOM ROX device models with firmware version below 2.17.1 that has administrative access enabled and feature key installation capability available.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.17.1 or later
Fixed in 2.17.1
Interim mitigation

Upgrade all affected devices to RUGGEDCOM ROX V2.17.1 or later. Limit administrative access to trusted personnel only and monitor for suspicious feature key installation activity until patching is complete.

Recommended fix High confidence

V2.17.1 or later

  1. 1. Identify the specific Ruggedcom ROX device model (MX5000, MX5000RE, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512, RX1524, RX1536, or RX5000)
  2. 2. Navigate to the Siemens cert-portal or Siemens support website to download firmware version V2.17.1 or later for your specific device model
  3. 3. Access the device web interface or CLI console using administrator credentials
  4. 4. Backup the current device configuration before performing the firmware upgrade
  5. 5. Upload the V2.17.1 firmware file through the device's firmware upgrade functionality (typically found under Administration > Firmware Upgrade or similar menu)
  6. 6. Wait for the firmware upload and installation to complete - do not power off the device during this process
  7. 7. After the device reboots, verify the firmware version has been updated to V2.17.1 or later
  8. 8. Restore the previously backed up configuration if needed
Caveat Review Siemens release notes for V2.17.1 for any configuration or feature compatibility changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ruggedcom Rox Mx5000 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-40947 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-40947 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data