# CVE-2026-24663: Copeland XWEB and XWEB Pro OS Command Injection

> Unauthenticated attackers can execute arbitrary code on Copeland XWEB controllers via OS command injection in the libraries installation route.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Feb 2026
- **Updated:** 2 Mar 2026
- **Also known as:** GHSA-5m2v-c6pj-9qqh

## What is CVE-2026-24663?

CVE-2026-24663 is a critical command injection vulnerability in Copeland XWEB 300D PRO, published on 27 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An OS command injection vulnerability exists in XWEB Pro version 1.12.1 
and prior, enabling an unauthenticated attacker to achieve remote code 
execution on the system by sending a crafted request to the libraries 
installation route and injecting malicious input into the request body.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-24663?

It affects 3 products.


Products: Copeland Xweb 300d Pro Firmware, Copeland Xweb 500b Pro Firmware, Copeland Xweb 500d Pro Firmware.

## How do I fix CVE-2026-24663?

No fix has been published for CVE-2026-24663 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-24663 being exploited?

There is no known exploitation of CVE-2026-24663 in the wild and no public exploit code.

## Other vulnerabilities in Copeland XWEB 300D PRO

- [CVE-2026-21718](https://insights.sbomify.com/CVE-2026-21718/): Copeland XWEB and XWEB Pro Use of a Broken or Risky Cryptographic Algorithm (critical 10.0)
- [CVE-2026-25085](https://insights.sbomify.com/CVE-2026-25085/): Copeland XWEB and XWEB Pro Unexpected Status Code or Return Value (high 8.6)
- [CVE-2026-20742](https://insights.sbomify.com/CVE-2026-20742/): Copeland XWEB and XWEB Pro OS Command Injection (high 8.0)
- [CVE-2026-20764](https://insights.sbomify.com/CVE-2026-20764/): Copeland XWEB and XWEB Pro OS Command Injection (high 8.0)
- [CVE-2026-20902](https://insights.sbomify.com/CVE-2026-20902/): Copeland XWEB and XWEB Pro OS Command Injection (high 8.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24663 and fix it if it is affected.

What it is: CVE-2026-24663 is a critical command injection vulnerability in Copeland XWEB 300D PRO, published on 27 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-24663 in the wild and no public exploit code.

Affected product: Copeland XWEB 300D PRO. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-24663/ (Markdown: https://insights.sbomify.com/CVE-2026-24663/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24663
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24663
- OSV: https://osv.dev/vulnerability/CVE-2026-24663

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-24663/
Summaries are generated and may contain mistakes; the official description above is the record.