CVE-2025-33023VulnerabilityPublished 12 Aug 2025

CVE-2025-33023: Siemens RUGGEDCOM ROX MX5000 · Unrestricted File Upload

Affects Siemens RUGGEDCOM ROX MX5000Source CVE Database V5

Not known to be exploited · CVSS 4.1 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Changed
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Siemens RUGGEDCOM ROX MX5000	Affected =0	Fixed in–

AI-suggested

1. Restrict access to the web interface of Siemens RUGGEDCOM devices strictly to trusted administrators using network segmentation, VPNs, or jump hosts to reduce exposure. 2. Enforce strong authentication mechanisms and regularly audit privileged accounts to prevent unauthorized access. 3. Monitor device logs and network traffic for unusual file upload activity or configuration changes indicative of exploitation attempts. 4. Implement strict file integrity monitoring on devices and connected systems to detect unauthorized file modifications or uploads. 5. Until an official patch is released, consider disabling or limiting file upload functionality if operationally feasible. 6. Employ network intrusion detection/prevention systems (IDS/IPS) with signatures or anomaly detection tailored for Siemens RUGGEDCOM devices to detect exploitation attempts. 7. Maintain an up-to-date asset inventory and ensure that all affected devices are identified and prioritized for remediation. 8. Engage with Siemens support channels to obtain patches or workarounds as soon as they become available and apply them promptly. 9. Conduct regular security training for administrators to recognize and prevent misuse of high-privilege access. These measures go beyond generic advice by focusing on operational controls, monitoring, and proactive management specific to the affected industrial devices and their typical deployment environments.

Description

A vulnerability has been identified in RUGGEDCOM ROX MX5000 (All versions), RUGGEDCOM ROX MX5000RE (All versions), RUGGEDCOM ROX RX1400 (All versions), RUGGEDCOM ROX RX1500 (All versions), RUGGEDCOM ROX RX1501 (All versions), RUGGEDCOM ROX RX1510 (All versions), RUGGEDCOM ROX RX1511 (All versions), RUGGEDCOM ROX RX1512 (All versions), RUGGEDCOM ROX RX1524 (All versions), RUGGEDCOM ROX RX1536 (All versions), RUGGEDCOM ROX RX5000 (All versions). The affected devices do not properly enforce the restriction of files that can be uploaded from the web interface. This could allow an authenticated remote attacker with high privileges in the web interface to upload arbitrary files.

Impact

For European organizations, particularly those operating critical infrastructure sectors such as energy, transportation, and manufacturing, this vulnerability poses a risk to the integrity of their industrial network devices. Siemens RUGGEDCOM devices are widely deployed in industrial control systems (ICS) and operational technology (OT) networks across Europe. An attacker with high-level web interface access could upload malicious files, potentially leading to unauthorized configuration changes, insertion of malware, or disruption of device operation. Although the vulnerability does not directly impact confidentiality or availability, integrity compromise in OT environments can lead to unsafe conditions, operational disruptions, or serve as a foothold for further attacks. The requirement for high privileges limits the attack surface to insiders or attackers who have already compromised credentials, but this does not eliminate risk, especially in environments where credential management or network segmentation is weak. The changed scope indicates that the impact could extend beyond the device itself, potentially affecting connected systems or networks. Given the critical role of these devices in industrial networks, the vulnerability could indirectly affect safety and operational continuity in European industrial sectors.

CWE-434Unrestricted Upload of File with Dangerous Type (opens in a new tab)
Base weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #12OWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.
Architecture and Design
Generate a new, unique filename for an uploaded file instead of using the user-supplied filename, so that no external input is used at all.
Architecture and Design · Enforcement by Conversion
When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
Architecture and Design
Consider storing the uploaded files outside of the web document root entirely. Then, use other mechanisms to deliver the files dynamically.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Web Service Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
File Upload (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V12.5.2 (opens in a new tab)
V13.1.5 (opens in a new tab)
V12.2.1 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

cert-portal.siemens.com/productcert/html/ssa-665108.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Aug 2025, 11:52 UTC

WeaknessesCWE-434

Technical details

References

Community reviews

Related threats