CVE-2026-25196: Copeland XWEB 300D PRO · OS Command Injection
Affects Copeland XWEB 300D PROSource CVE Database V5
Not known to be exploited · CVSS 8.0 High.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 2.0% chance of exploitation in 30 days – higher than 81% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 27 Feb 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 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| CopelandCopeland XWEB 300D PRO | Affected
| Fixed in– |
| CopelandCopeland XWEB 500D PRO | Affected
| Fixed in– |
| CopelandCopeland XWEB 500B PRO | Affected
| Fixed in– |
AI-suggested
Organizations should implement the following specific mitigations: 1) Restrict and tightly control administrative access to the Copeland XWEB 300D PRO management interfaces, using network segmentation and strong authentication mechanisms to limit exposure. 2) Monitor and audit configuration changes, especially those involving Wi-Fi SSID and password fields, to detect anomalous or unauthorized input. 3) Employ input validation and sanitization at the network perimeter or via proxy solutions if possible, to filter suspicious payloads targeting configuration parameters. 4) Maintain strict credential management policies, including regular password changes and use of multi-factor authentication if supported. 5) Engage with the vendor for timely patch releases and apply updates as soon as they become available. 6) Consider deploying intrusion detection or prevention systems tailored to detect command injection patterns or unusual device behavior. 7) For critical environments, isolate affected devices from less trusted networks to reduce the risk of lateral movement. 8) Conduct regular security assessments and penetration testing focusing on device management interfaces to identify potential weaknesses before exploitation.
Description
An OS command injection vulnerability exists in XWEB Pro version 1.12.1 and prior, enabling an authenticated attacker to achieve remote code execution on the system by injecting malicious input into the Wi-Fi SSID and/or password fields can lead to remote code execution when the configuration is processed.