Skip to main content
Menu
CVEs

Copeland XWEB EVO pre-auth command injection via username field

Affects Copeland XWEB EVO versions 5.2.3 through before 5.7.0. The checked facts list no fixed version or patch.

CVE-2026-124002EUVD-2026-124635GHSA-6FGF-7RXH-228QPublished November 12, 2026, updated Needs attention

9.3CriticalCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 5.7.0
Who is exposed
Not reported

Summary

Copeland's XWEB EVO is affected by a flaw that lets a remote attacker, without logging in, run arbitrary operating system commands by injecting shell characters into the username field before the password check. Because the attacker can combine this with a root-level interpreter on the device, they could gain full control of the system.

Written by a model

Original description

XWEB EVO versions 5.2.3 through before 5.7.0 contains a pre-authentication OS command injection vulnerability that allows unauthenticated remote attackers to execute arbitrary OS commands by injecting shell metacharacters into the username field of login.lua, cleanout.lua, or api.lua before the password check occurs. Attackers can exploit this flaw combined with the setuid-root wlua interpreter to execute commands with root privileges, achieving full system compromise. This product line reached it's end of service date in March 2026.

Who should check

Teams running Copeland/Dixell XWEB EVO controllers, versions 5.2.3 through before 5.7.0. The product line reached end of service in March 2026.

“XWEB EVO versions 5.2.3 through before 5.7.0”

vulncheck.com

What to do

Upgrade to a fixed version: 5.7.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-124002 (Dixell/Copeland XWEB EVO Pre-Auth OS Command Injection via Username), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-124002 (entry last updated 2026-11-13):
Affected:
- Copeland XWEB EVO: from 5.2.3, fixed in 5.7.0
Fixed versions: 5.7.0.
Conditions (all must be true for the bug to be hit):
- Product is XWEB EVO versions 5.2.3 through before 5.7.0 (source: https://www.vulncheck.com/advisories/dixell-copeland-xweb-evo-pre-authentication-os-command-injection-via-username)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-124002 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-124002 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://webapps.copeland.com/dixell/Content/Pages/AdvertisingMaterials/ProductNews/XWEB%20EVO%20EoS%20-%20Product_Bulletin_March_2026.pdf
- https://webapps.copeland.com/Dixell/Pages/SystemSoftwareUpdate
- https://www.vulncheck.com/advisories/dixell-copeland-xweb-evo-pre-authentication-os-command-injection-via-username
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-124002
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-124002"}.

Affected versions

cve.now Index

58of 100 · methodology v3
  • Exploitation28/40Public exploit, and a Nuclei detection template
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.3, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 63 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now1 day
  4. CISA SSVC assessment

    Exploitation: poc · Automatable: yes · Technical impact: total

  5. Record last updated2 days
  6. Exploit code on GitHub

    fixedbyreboot/CVE-2026-124002-POC

Public exploit activity

10Posted on X by cve.nowNuclei template listed100%0Nov 12Nov 22
  • GitHub PoC repos: 1
  • EPSS: 9.69%
  • Posted on X by cve.now Nov 12
  • Nuclei template listed Nov 19

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

On X 1

Evidence 8

Questions about CVE-2026-124002

Is CVE-2026-124002 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. Public exploit code exists (a proof of concept on GitHub).

Source: cve.now feed data

What does this mean?

An unauthenticated remote attacker can inject operating system commands through the Username field and run them with root privileges, which can fully compromise the system.

Source: vulncheck.com

Which versions are affected by CVE-2026-124002?

XWEB EVO: from 5.2.3 before 5.7.0.

Source: cve.now feed data

Am I affected, and how do I check?

Copeland XWEB EVO versions 5.2.3 up to but not including 5.7.0 are in the affected range. To check a device, compare the firmware or software version it reports against that range.

Source: vulncheck.com

How do I fix CVE-2026-124002?

The checked facts name no fixed version, patch, or workaround, so no upgrade target is given here. Check the vendor's advisory for a patch before relying on any version.

Source: vulncheck.com

No corrections so far. Something wrong on this page? Report an error.