CVE-2025-41709
PROBLEMTYPE] in [VENDOR] [PRODUCT] [COMPONENT] Allows [IMPACT
Publication date: 2026-03-10
Last updated on: 2026-03-18
Assigner: CERT VDE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| janitza | umg_96rm_e | to 3.13 (inc) |
| weidmueller | energy_meter_750_230 | to 3.13 (inc) |
| weidmueller | energy_meter_750_24 | to 3.13 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-78 | The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-41709 is a critical OS command injection vulnerability (CWE-78) affecting Janitza UMG 96RM-E power analyzers and Weidmueller Energy Meter models 750-24 and 750-230 with firmware versions up to 3.13.
An unauthenticated remote attacker can exploit this vulnerability via Modbus-TCP or Modbus-RTU protocols to inject OS commands, gaining read and write access on the affected device.
Successful exploitation can lead to full system compromise, including remote code execution, allowing the attacker to control the device completely.
This vulnerability is part of a set of multiple security issues in these devices, all fixed by updating to firmware version 3.14 or later.
How can this vulnerability impact me? :
Exploitation of CVE-2025-41709 allows an unauthenticated remote attacker to gain full read and write access to the affected device.
This can lead to complete system compromise, including remote code execution, which may disrupt device operation, cause data loss, or allow the attacker to manipulate device functions.
Such control over critical energy monitoring devices could impact operational availability, data integrity, and confidentiality.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves OS command injection via Modbus-TCP or Modbus-RTU protocols on affected devices. Detection can focus on monitoring Modbus traffic for unusual or unauthorized commands that could indicate exploitation attempts.
Network detection might include capturing and analyzing Modbus packets for suspicious payloads or commands that attempt to inject OS commands.
On the affected devices, checking the firmware version is critical since versions 3.13 and earlier are vulnerable.
- Use network packet capture tools (e.g., Wireshark or tcpdump) to monitor Modbus-TCP or Modbus-RTU traffic for suspicious command patterns.
- Run commands or scripts to query the device firmware version to verify if it is 3.13 or earlier.
- Look for unexpected read/write operations or commands on the device that could indicate exploitation.
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation step is to update the firmware of affected devices to version 3.14 or later, where this vulnerability and related issues have been fixed.
Additional immediate steps include restricting network access to the affected devices by limiting Modbus protocol exposure to trusted networks only.
Changing default passwords and credentials on the devices is also recommended to reduce the risk of unauthorized access.