Skip to main content
VulnerabilityPublished

CVE-2025-41734: METZ CONNECT Energy-Controlling EWIO2-M · PHP Remote File Inclusion

Affects METZ CONNECT Energy-Controlling EWIO2-MSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
METZ CONNECT Energy-Controlling EWIO2-MAffected
  • =0.0.0
Fixed in–

AI-suggested

  1. Immediately restrict network access to the EWIO2-M devices by implementing strict firewall rules and network segmentation, isolating these devices from general IT networks and the internet.
  2. Monitor network traffic for unusual requests targeting PHP include or require functions on the device.
  3. Disable or restrict remote management interfaces if not necessary, or enforce VPN and strong authentication mechanisms for remote access.
  4. Apply vendor patches or firmware updates as soon as they become available; maintain close communication with METZ CONNECT for updates.
  5. Conduct regular security audits and vulnerability assessments on energy management systems to detect similar issues.
  6. Implement intrusion detection/prevention systems (IDS/IPS) tuned to detect remote file inclusion attempts.
  7. Employ application-layer filtering to sanitize inputs and block suspicious payloads targeting PHP file inclusion.
  8. Maintain comprehensive logging and monitoring to detect exploitation attempts early.
  9. Develop and test incident response plans specific to industrial control system compromises.

Description

An unauthenticated remote attacker can execute arbitrary php files and gain full access of the affected devices.

References

Community reviews

Loading reviews…