CVE-2025-41735 Details
Description
A low privileged remote attacker can upload any file to an arbitrary location due to missing file check resulting in remote code execution.
A vulnerability allowing remote code execution has been identified in METZ CONNECT EWIO2 series devices, specifically in the Energy-Controlling EWIO2-M, EWIO2-M-BM, and Ethernet-IO EWIO2-BM models, all running firmware prior to 2.2.0. This issue arises from inadequate file validation, which enables low-privileged remote attackers to upload files to arbitrary locations on the device.
Users are advised to update to version 2.2.0 or later. Schedule the update during the next maintenance window.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Nov 18, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://certvde.com/de/advisories/VDE-2025-097 | [email protected] | Third Party Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-434 | Unrestricted Upload of File with Dangerous Type | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| metz-connect ewio2-m firmware | < 2.2.0 |
CPE
Remediation
| |
| metz-connect ewio2-m | All versions |
CPE
Remediation
| |
| metz-connect ewio2-m-bm firmware | < 2.2.0 |
CPE
Remediation
| |
| metz-connect ewio2-m-bm | All versions |
CPE
Remediation
| |
| metz-connect ewio2-bm firmware | < 2.2.0 |
CPE
Remediation
| |
| metz-connect ewio2-bm | All versions |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 18, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Nov 21, 2025 | Initial Analysis | [email protected] |
| Nov 18, 2025 | New CVE Received | [email protected] |