CVE-2023-36751

HIGH
7.2
CVSS Score
Published: July 11, 2023 at 09:07 AM UTC
Updated: October 23, 2026 at 11:10 PM UTC
22 products affected across 1 vendorRUGGEDCOM Rox RX1510 FirmwareRUGGEDCOM Rox RX1511 FirmwareRUGGEDCOM Rox MX5000 Firmware· also runs on 11 platforms

Using RUGGEDCOM ROX MX5000 by Siemens?

Get instant alerts when new vulnerabilities affect RUGGEDCOM ROX MX5000 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.2
Exploit prediction
EPSS 2%
SSVC
No known exploit

Description

A vulnerability has been identified in RUGGEDCOM ROX MX5000 (All versions < V2.16.0), RUGGEDCOM ROX MX5000RE (All versions < V2.16.0), RUGGEDCOM ROX RX1400 (All versions < V2.16.0), RUGGEDCOM ROX RX1500 (All versions < V2.16.0), RUGGEDCOM ROX RX1501 (All versions < V2.16.0), RUGGEDCOM ROX RX1510 (All versions < V2.16.0), RUGGEDCOM ROX RX1511 (All versions < V2.16.0), RUGGEDCOM ROX RX1512 (All versions < V2.16.0), RUGGEDCOM ROX RX1524 (All versions < V2.16.0), RUGGEDCOM ROX RX1536 (All versions < V2.16.0), RUGGEDCOM ROX RX5000 (All versions < V2.16.0). The install-app URL parameter in the web interface of affected devices is vulnerable to command injection due to missing server side input sanitation. This could allow an authenticated privileged remote attacker to execute arbitrary code with root privileges.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Affected range stops below 2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below V2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below v2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below v2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below v2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below v2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below v2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below v2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below v2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below v2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below v2.16.0, so it looks safe — our inference, not a vendor statement

Runs on — not affected

The affected product only carries this flaw when running on these platforms. The platforms themselves are not vulnerable.

Affected range stops below 2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below V2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below v2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below v2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below v2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below v2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below v2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below v2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below v2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below v2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.16.0, so it looks safe — our inference, not a vendor statement
Affected range stops below v2.16.0, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
HIGH
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-77

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card