Skip to main content
CVE-2025-41663VulnerabilityPublished Updated

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

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

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 50% 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 11 Jun 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Weidmueller IE-SR-2TX-WLAffected
  • =0
Fixed in–

AI-suggested

1. Immediately audit and secure all proxy configurations to eliminate insecure setups that allow man-in-the-middle interception. This includes enforcing strict proxy authentication, using trusted proxy servers, and disabling any transparent or unauthenticated proxies. 2. Implement network segmentation to isolate Weidmueller IE-SR-2TX-WL devices from general IT networks and restrict access to management interfaces only to trusted hosts. 3. Employ encrypted communication channels (e.g., TLS) with certificate validation between clients and WWH servers to prevent interception and manipulation of traffic. 4. Monitor network traffic for unusual patterns indicative of MitM attacks or command injection attempts, using intrusion detection systems tailored for industrial protocols. 5. Engage with Weidmueller for patches or firmware updates addressing this vulnerability as soon as they become available and apply them promptly. 6. Conduct regular security training for network administrators to recognize and remediate insecure proxy configurations and MitM risks. 7. Consider deploying endpoint protection solutions capable of detecting anomalous command executions on affected devices. These steps go beyond generic advice by focusing on the specific exploitation vector (insecure proxies) and the operational context of the affected product.

Description

For u-link Management API an unauthenticated remote attacker in a man-in-the-middle position can inject arbitrary commands in responses returned by WWH servers, which are then executed with elevated privileges. To get into such a position, clients would need to use insecure proxy configurations.

References

Community reviews

Loading reviews…