CVE Intelligence
High Injection

CVE-2023-36752 — A vulnerability has been identified in RUGGEDCOM ROX MX5000 (All versions < V2.16.0), RUGGEDCOM...

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 upgrade-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.

Published Jul 11, 2023 · Updated Oct 23, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: siemens

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 1.5% (30-day exploitation probability)+11
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
1.54%
ahead of 75% of scored CVEs · Oct 26, 2026
Affects
Siemens
RUGGEDCOM ROX MX5000 and 21 more
CVSS base
7.2
High · 4 source(s)
Prioritization reference: 9.1 provisional

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Siemens RUGGEDCOM ROX MX5000, Siemens Ruggedcom Rox Mx5000 Firmware, Siemens RUGGEDCOM ROX MX5000RE…).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Siemens RUGGEDCOM ROX MX5000 version All versions < V2.16.0 Vulnerable CVE Program (cve.org) e CISA ADP
Siemens Ruggedcom Rox Mx5000 Firmware < 2.16.0 Vulnerable NIST National Vulnerability Database
Siemens RUGGEDCOM ROX MX5000RE version All versions < V2.16.0 Vulnerable CVE Program (cve.org) e CISA ADP
Siemens Ruggedcom Rox Mx5000re Firmware < 2.16.0 Vulnerable NIST National Vulnerability Database
Siemens RUGGEDCOM ROX RX1400 version All versions < V2.16.0 Vulnerable CVE Program (cve.org) e CISA ADP
Siemens Ruggedcom Rox Rx1400 Firmware < 2.16.0 Vulnerable NIST National Vulnerability Database
Siemens RUGGEDCOM ROX RX1500 version All versions < V2.16.0 Vulnerable CVE Program (cve.org) e CISA ADP
Siemens Ruggedcom Rox Rx1500 Firmware < 2.16.0 Vulnerable NIST National Vulnerability Database
Siemens RUGGEDCOM ROX RX1501 version All versions < V2.16.0 Vulnerable CVE Program (cve.org) e CISA ADP
Siemens Ruggedcom Rox Rx1501 Firmware < 2.16.0 Vulnerable NIST National Vulnerability Database
Siemens RUGGEDCOM ROX RX1510 version All versions < V2.16.0 Vulnerable CVE Program (cve.org) e CISA ADP
Siemens Ruggedcom Rox Rx1510 Firmware < 2.16.0 Vulnerable NIST National Vulnerability Database
Siemens RUGGEDCOM ROX RX1511 version All versions < V2.16.0 Vulnerable CVE Program (cve.org) e CISA ADP
Siemens Ruggedcom Rox Rx1511 Firmware < 2.16.0 Vulnerable NIST National Vulnerability Database
Siemens RUGGEDCOM ROX RX1512 version All versions < V2.16.0 Vulnerable CVE Program (cve.org) e CISA ADP
Siemens Ruggedcom Rox Rx1512 Firmware < 2.16.0 Vulnerable NIST National Vulnerability Database
Siemens RUGGEDCOM ROX RX1524 version All versions < V2.16.0 Vulnerable CVE Program (cve.org) e CISA ADP
Siemens Ruggedcom Rox Rx1524 Firmware < 2.16.0 Vulnerable NIST National Vulnerability Database
Siemens RUGGEDCOM ROX RX1536 version All versions < V2.16.0 Vulnerable CVE Program (cve.org) e CISA ADP
Siemens Ruggedcom Rox Rx1536 Firmware < 2.16.0 Vulnerable NIST National Vulnerability Database
Siemens RUGGEDCOM ROX RX5000 version All versions < V2.16.0 Vulnerable CVE Program (cve.org) e CISA ADP
Siemens Ruggedcom Rox Rx5000 Firmware < 2.16.0 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
9.1 CVSS 3.1 Critical 2.3 6.0 productcert@siemens.com via NIST National Vulnerability Database
9.1 CVSS 3.1 Critical — — GitHub, Inc. via GitHub Security Advisories
9.1 CVSS 3.1 Critical — — siemens via CVE Program (cve.org) e CISA ADP
7.2 CVSS 3.1 High 1.2 5.9 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)
Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 9.1 (productcert@siemens.com via NIST National Vulnerability Database) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-77 · Command Injection

Other CVEs with this weakness →

EPSS over time FIRST

Oct 23, 2026 → Oct 26, 2026 · 4 reading(s) · max 1.54%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Look for parameters with command/query metacharacters and unexpected child processes of the service.
web/proxy/WAF logsnetwork IDS/IPSapplication logsendpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · siemens/ruggedcom rox mx5000, siemens/ruggedcom rox mx5000re, siemens/ruggedcom rox rx1400, siemens/ruggedcom rox rx1500
    Oct 23, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 23, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 23, 2026
  • Affected products added · siemens/ruggedcom rox mx5000 firmware, siemens/ruggedcom rox mx5000re firmware, siemens/ruggedcom rox rx1400 firmware, s
    Oct 23, 2026 · NIST National Vulnerability Database
  • CVSS changed · 7.2
    Oct 23, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 23, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 23, 2026 · Alertas do Telegram
  • 2023
  • CVE published
    Jul 11, 2023 · siemens

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 23, 2026 – Oct 23, 2026
  • 1× Official description updated · Oct 23, 2026 – Oct 23, 2026

References

3 on the record

Elsewhere on this site

Siemens
every CVE for this vendor
Injection
same class
CWE-77
other pages naming this weakness

Related CVEs (same products)

  • Medium CVE-2025-40948 A vulnerability has been identified in RUGGEDCOM ROX MX5000 (All versions < V2.17.1), RUGGEDCOM... May 12, 2026
  • Critical CVE-2025-40949 A vulnerability has been identified in RUGGEDCOM ROX MX5000 (All versions < V2.17.1), RUGGEDCOM... May 12, 2026
  • High CVE-2025-40947 A vulnerability has been identified in RUGGEDCOM ROX MX5000 (All versions < V2.17.1), RUGGEDCOM... May 12, 2026
  • High CVE-2024-56839 A vulnerability has been identified in RUGGEDCOM ROX II family (All versions < V2.17.0). Code... Dec 9, 2025
  • High CVE-2024-56838 A vulnerability has been identified in RUGGEDCOM ROX II family (All versions < V2.17.0). The SCEP... Dec 9, 2025
  • High CVE-2024-56840 A vulnerability has been identified in RUGGEDCOM ROX II family (All versions < V2.17.0). Under... Dec 9, 2025

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2023-36752 is "A vulnerability has been identified in RUGGEDCOM ROX MX5000 (All versions < V2.16.0), RUGGEDCOM...", rated High. It affects RUGGEDCOM ROX MX5000 (Siemens); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.2 describes technical severity. EPSS 1.54% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.