VulnerabilityPublished 10 Mar 2026

CVE-2025-41712: Janitza UMG 96RM-E 24V(5222063) · Incorrect Permissions

Affects Janitza UMG 96RM-E 24V(5222063)Source CVE Database V5

Compare

Not known to be exploited · CVSS 6.5 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

6.5Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within 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 10 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 Oct 2026.

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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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
JanitzaUMG 96RM-E 24V(5222063)	Affected <=3.13	Fixed in–
JanitzaUMG 96RM-E 230V(5222062)	Affected <=3.13	Fixed in–
WeidmuellerENERGY METER 750-230 (2540910000)	Affected <=3.13	Fixed in–
WeidmuellerENERGY METER 750-24 (2540900000)	Affected <=3.13	Fixed in–

AI-suggested

To mitigate CVE-2025-41712, organizations should implement strict access controls on the Janitza UMG 96RM-E 24V web interface, limiting user permissions and restricting upload capabilities to trusted personnel only. User training to recognize and avoid uploading untrusted or manipulated files is critical to prevent social engineering exploitation. Network segmentation should isolate the device from general user networks to reduce exposure to unauthenticated attackers. Monitoring and logging of file upload activities on the device can help detect suspicious behavior early. Until an official patch is released, consider disabling or restricting the web server’s file upload functionality if possible. Employ web application firewalls or intrusion detection systems to detect and block malicious payloads targeting the device’s web interface. Regularly check for firmware updates from Janitza and apply them promptly once available. Additionally, conduct security audits of device configurations to ensure permissions are appropriately assigned and no unnecessary services are exposed.

Description

An unauthenticated remote attacker who tricks a user to upload a manipulated HTML file can get access to sensitive information on the device. This is a result of incorrect permission assignment for the web server.

Impact

The primary impact of CVE-2025-41712 is unauthorized disclosure of sensitive information from the Janitza UMG 96RM-E 24V device. This could include operational data, configuration details, or other critical information that could aid further attacks or industrial espionage. Since the device is used in energy monitoring and management, exposure of such data could compromise operational security and privacy. Although the vulnerability does not allow modification or disruption of device functions, the leakage of sensitive data can undermine trust and potentially facilitate subsequent attacks on industrial control systems or energy infrastructure. Organizations relying on these devices in critical infrastructure sectors such as utilities, manufacturing, and energy distribution are at risk of information leakage that could have cascading effects on operational security. The requirement for user interaction limits mass exploitation but targeted spear-phishing or social engineering campaigns could be effective. The lack of authentication requirement for the attacker increases the risk profile, especially in environments where device access is not tightly controlled.

CWE-732Incorrect Permission Assignment for Critical Resource (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
Implementation
When using a critical resource such as a configuration file, check to see if the resource has insecure permissions (such as being modifiable by any regular user), and generate an error or even exit the software if there is a possibility that the resource could have been modified by an unauthorized party.
Architecture and Design
Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully defining distinct user groups, privileges, and/or roles. Map these against data, functionality, and the related resources. Then set the permissions accordingly.
Architecture and Design · Operation · Sandbox or Jail
Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V4.3.3 (opens in a new tab)
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
Directory Indexing (opens in a new tab)
Using Malicious Files (opens in a new tab)
Exploiting Incorrectly Configured Access Control Security Levels (opens in a new tab)
Signing Malicious Code (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Mar 2026, 08:48 UTC

WeaknessesCWE-732

Technical details

References

Community reviews

Related threats