CVE
Copeland XWEB EVO remote command execution as root in backup.lua
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Copeland XWEB EVO versions 5.2.3 through 5.8.8 Exploitable through the output device path parameter processed by backup.lua
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 2.33% · 83rd percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Copeland XWEB EVO has an OS command injection flaw in its backup.lua component, where shell metacharacters in the output device path parameter are passed unescaped into system commands. An attacker who is logged in with high privileges can reach this remotely over the network and run arbitrary commands as root, gaining full control of the system.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
XWEB EVO 5.2.3 through 5.8.8 contains an authenticated OS command injection vulnerability that allows authenticated attackers to execute arbitrary commands as root by injecting shell metacharacters into the output device path parameter processed by backup.lua. Attackers can exploit the unescaped concatenation into mount, unzip, and related shell commands run via the wlua interpreter, including through the setuid xwbackup.cgi and xwrestore.cgi interfaces, to achieve full system compromise. This product line reached it's end of service date in March 2026.
Who should check
Teams running Copeland XWEB EVO controllers, versions 5.2.3 through 5.8.8, including those using the xwbackup.cgi and xwrestore.cgi interfaces
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.6/10CVSS 8.6
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Copeland XWEB EVO versions 5.2.3 through 5.8.8 Exploitable through the output device path parameter processed by backup.luaApply the patch listed under Evidence.
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-124009 (Dixell/Copeland XWEB EVO OS Command Injection via backup.lua), 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-124009 (entry last updated 2026-11-12):
Affected:
- Copeland XWEB EVO: from 5.2.3, through 5.8.8
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Copeland XWEB EVO versions 5.2.3 through 5.8.8 (source: https://www.vulncheck.com/advisories/dixell-copeland-xweb-evo-os-command-injection-via-backup-lua)
- Exploitable through the output device path parameter processed by backup.lua (source: https://www.vulncheck.com/advisories/dixell-copeland-xweb-evo-os-command-injection-via-backup-lua)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-124009 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-124009 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-os-command-injection-via-backup-lua
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-124009
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-124009"}.Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- Copeland XWEB EVO
From 5.2.3 · through 5.8.8
Evidence 5
Vendor advisory · 2
Establishes: Affected and fixed versions.
- Advisory
- Patch
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-124009
Is CVE-2026-124009 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. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Shell metacharacters injected into the output device path parameter that backup.lua processes can make the device run arbitrary commands as root, which can lead to full system compromise.Source: vulncheck.com
Which versions are affected by CVE-2026-124009?
XWEB EVO: from 5.2.3 through 5.8.8.Source: cve.now feed data
Am I affected, and how do I check?
Copeland XWEB EVO versions 5.2.3 through 5.8.8 are listed as affected. To check a device, look up its XWEB EVO software version and compare it with that range.Source: vulncheck.com
How do I fix CVE-2026-124009?
The checked facts name no fixed version or vendor patch IDs, so they give no upgrade target. Check Copeland's advisory for a fix before relying on any version.Source: vulncheck.com