Skip to main content
VulnerabilityPublished Updated

CVE-2026-24517: 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
1.8% chance of exploitation in 30 days – higher than 78% 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

  1. Immediately restrict network access to the management interface of Copeland XWEB 300D PRO devices, limiting it to trusted administrators and secure management networks only.
  2. Implement strong authentication and access controls to prevent unauthorized access, including multi-factor authentication if supported.
  3. Monitor network traffic and device logs for unusual or suspicious activity related to firmware update requests or command execution attempts.
  4. Employ network segmentation to isolate these devices from critical systems and limit lateral movement in case of compromise.
  5. Until a patch is released, consider disabling remote firmware update functionality if operationally feasible.
  6. Engage with the vendor for updates on patches or mitigations and apply them promptly once available.
  7. Conduct regular security assessments and penetration tests focusing on device management interfaces.
  8. Educate administrators on the risks of command injection and the importance of secure device configuration.

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 requests sent to the firmware update route.

References

Community reviews

Loading reviews…