CVE-2025-40949
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 · uneditedA 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.
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 confidenceA command injection vulnerability exists in the Scheduler functionality of the RUGGEDCOM ROX web UI. User-supplied input is not properly sanitized, allowing authenticated attackers to inject arbitrary OS commands that execute with root privileges on the underlying Linux-based system.
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< 2.17.1< 2.17.1< 2.17.1< 2.17.1< 2.17.1< 2.17.1< 2.17.1< 2.17.1CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify your RUGGEDCOM ROX device modelAccess the web interface and navigate to the device status or system information page to confirm the exact model (Mx5000, Mx5000re, Rx1400, Rx1500, Rx1501, Rx1510, Rx1511, or Rx1512)Affected if The device model is any of the listed affected products (Mx5000, Mx5000re, Rx1400, Rx1500, Rx1501, Rx1510, Rx1511, or Rx1512)
-
Check the installed firmware versionIn the web interface, go to System > Firmware or System > About to view the current firmware version. Compare it against the vulnerable threshold of 2.17.1Affected if The firmware version is below 2.17.1 (for example, 2.16.0, 2.15.3, etc.)
-
Verify if the Scheduler feature is accessibleLog into the web interface and navigate to the Scheduler or Task Scheduler menu. Confirm whether this feature is present and accessible with your current user accountAffected if The Scheduler functionality is present and accessible to your authenticated user account
-
Check for existing scheduler tasksIn the Scheduler interface, review any configured tasks to see if they contain unusual or unexpected command strings, particularly looking for shell metacharacters like ; | & $ ` or command substitutionsAffected if Any scheduled tasks contain suspicious command patterns or unexpected OS command syntax
You are affected if you are running any of the listed RUGGEDCOM ROX models with firmware version below 2.17.1 and the Scheduler feature is accessible to authenticated users on your network.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.17.1
Apply vendor firmware patch V2.17.1 or later to all affected RUGGEDCOM ROX devices. Until patched, restrict web UI access to trusted administrative users only and monitor for suspicious scheduler activity.
V2.17.1 or later
- Identify the exact Ruggedcom ROX device model from the affected list (MX5000, MX5000RE, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512)
- Obtain the V2.17.1 firmware image from the official Siemens cert-portal.siemens.com or Siemens industrial security website
- Review the firmware upgrade procedure in the Ruggedcom ROX installation/operation manual
- Perform a backup of the current device configuration
- Upload and apply firmware V2.17.1 or later via the Web UI or management interface
- Verify the upgrade was successful and the Scheduler functionality is operational
- Confirm the device is running the patched firmware version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-40949 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-40949 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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