Skip to main content
VulnerabilityPublished Updated

CVE-2026-21389: 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, 11:52 UTC

CVSS 3.1 base score
8.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.6% chance of exploitation in 30 days – higher than 77% 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 30 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-21389, organizations should implement the following specific measures: 1) Restrict network access to the Copeland XWEB 300D PRO devices, limiting connections to trusted administrators and management networks only. 2) Enforce strong authentication and access control policies to prevent unauthorized or low-privilege users from gaining high privilege access. 3) Monitor logs and network traffic for unusual activity related to the contacts import functionality or unexpected command execution attempts. 4) Disable or restrict the contacts import feature if not essential to reduce the attack surface. 5) Employ application-layer firewalls or intrusion prevention systems capable of detecting and blocking command injection patterns in HTTP request bodies. 6) Maintain an inventory of affected devices and track vendor communications for patches or updates, applying them promptly once available. 7) Conduct regular security assessments and penetration tests focusing on authentication mechanisms and input validation controls. 8) Educate administrators on the risks of this vulnerability and the importance of credential security to prevent privilege escalation. These targeted actions go beyond generic advice by focusing on access restriction, monitoring, and feature control specific to the vulnerable component.

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 request body sent to the contacts import route.

References

Community reviews

Loading reviews…