Skip to main content
VulnerabilityPublished Updated

CVE-2026-24452: Copeland XWEB 300D PRO · OS Command Injection

Affects Copeland XWEB 300D PROSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.0 High.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
8.0High
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
CopelandCopeland XWEB 300D PROAffected
  • <=1.12.1
Fixed in–
CopelandCopeland XWEB 500D PROAffected
  • <=1.12.1
Fixed in–
CopelandCopeland XWEB 500B PROAffected
  • <=1.12.1
Fixed in–

AI-suggested

To mitigate CVE-2026-24452, organizations should implement the following specific measures: 1) Immediately restrict access to the Copeland XWEB 300D PRO management interfaces to trusted personnel and networks using network segmentation and firewall rules. 2) Enforce strong authentication mechanisms and regularly audit user accounts to minimize the risk of credential compromise. 3) Implement strict input validation and sanitization on any user-supplied data, especially template files, to prevent injection attacks. 4) Monitor device logs and network traffic for unusual activities indicative of exploitation attempts. 5) Develop and deploy compensating controls such as application-layer firewalls or intrusion prevention systems tailored to detect command injection patterns. 6) Coordinate with Copeland for timely patch releases and apply firmware updates as soon as they become available. 7) Conduct regular security assessments and penetration testing focused on industrial control systems to identify and remediate similar vulnerabilities proactively.

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 supplying a crafted template file to the devices route.

References

Community reviews

Loading reviews…