dbcve.org
Ruggedcom Rox Mx5000 FirmwareOperating system · Siemens

CVE-2025-40948

MEDIUM · 6.8 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 2.17.1 or later.
See remediation →
74/100
Remediation priority · Elevated
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 validate input in the web server's JSON-RPC interface. This could allow an authenticated remote attacker to read arbitrary files from the underlying operating system's filesystem with root privileges.

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

The RUGGEDCOM ROX web server's JSON-RPC interface fails to properly validate input, allowing an authenticated remote attacker to perform path traversal and read arbitrary files from the filesystem with root privileges.

MitigationUpgrade all affected RUGGEDCOM ROX devices to firmware version V2.17.1 or later. If immediate patching is not possible, restrict network access to the management interface using firewalls or ACLs.

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
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

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

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 the device model
    Access the device CLI or web interface and retrieve the exact model name (Mx5000, Mx5000re, Rx1400, Rx1500, Rx1501, Rx1510, Rx1511, or Rx1512)
    Affected if The device model is not one of these eight RUGGEDCOM ROX models - the CVE does not apply
  2. Check the firmware version
    In the device's web interface, navigate to the System Information or About page, or use the CLI command 'show version' to retrieve the installed firmware version
    Affected if The firmware version is lower than 2.17.1 (for example, 2.16.0, 2.15.3, etc.)
  3. Verify the JSON-RPC interface is enabled
    In the web interface, go to the Configuration > Network Services or similar section and confirm whether the JSON-RPC service is active and accessible on port 443 or 80
    Affected if The JSON-RPC web interface is enabled and reachable on the network
  4. Confirm authentication is configured
    Check if there are user accounts configured on the device with valid credentials for the web interface
    Affected if Valid user credentials exist for the web interface - an attacker needs these credentials to exploit the path traversal

The device is affected if it is one of the eight listed RUGGEDCOM ROX models, runs firmware below version 2.17.1, has the JSON-RPC interface enabled, and has configured user accounts that could be used for authentication.

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 RUGGEDCOM ROX devices to firmware version V2.17.1 or later. If immediate patching is not possible, restrict network access to the management interface using firewalls or ACLs.

Recommended fix High confidence

Ruggedcom ROX firmware V2.17.1

  1. 1. Obtain the Ruggedcom ROX firmware version 2.17.1 from the Siemens cert-portal or official Siemens support channels
  2. 2. Access the device management interface using administrative credentials
  3. 3. Navigate to the firmware upgrade section in the device web interface or CLI
  4. 4. Upload and install the firmware version 2.17.1 following Siemens documented upgrade procedures
  5. 5. After upgrade completes, verify the device is running firmware version 2.17.1 or higher
  6. 6. Confirm the JSON-RPC interface now properly validates input and the vulnerability is resolved

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

Fix this in Ruggedcom Rox Mx5000 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-40948 — 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-40948 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