Skip to main content
VulnerabilityPublished

CVE-2025-41683: Weidmueller IE-SR-2TX-WL · OS Command Injection

Affects Weidmueller IE-SR-2TX-WLSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 14:05 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Jul 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
Weidmueller IE-SR-2TX-WLAffected
  • =0.0
Fixed in–

AI-suggested

European organizations using the Weidmueller IE-SR-2TX-WL should immediately assess their exposure to this vulnerability. Specific mitigation steps include: 1) Restrict access to the device's web interface to trusted management networks only, using network segmentation and firewall rules to limit exposure. 2) Enforce strong authentication mechanisms and rotate credentials regularly to reduce the risk of credential compromise. 3) Monitor device logs and network traffic for unusual activity indicative of exploitation attempts, focusing on the 'event_mail_test' endpoint usage. 4) Implement strict input validation and sanitization on any custom integrations or management scripts interacting with the device, if applicable. 5) Engage with Weidmueller support or authorized vendors to obtain patches or firmware updates as soon as they become available. 6) Consider deploying intrusion detection/prevention systems (IDS/IPS) tuned to detect command injection patterns targeting this device. 7) Conduct regular security audits and penetration testing of OT networks to identify and remediate similar vulnerabilities proactively.

Description

An authenticated remote attacker can execute arbitrary commands with root privileges on affected devices due to lack of improper sanitizing of user input in the Main Web Interface (endpoint event_mail_test).

References

Community reviews

Loading reviews…