Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2026-124010: Unauthenticated Root Command Injection in Copeland XWEB EVO

Published Nov 12, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days16 mentions · peak 6 in a dayToday
CVSS9.3Critical · v4
EPSS3.1%88th percentile
CISA KEVNoNot listed
In the wildReported4 exploitation records in Mallory
IdentifiersCVE-2026-124010CWE-78 · Improper Neutralization of Special…

CVE-2026-124010 is an operating-system command injection vulnerability affecting Copeland XWEB EVO, formerly branded Dixell, versions before 5.6.2. A setuid-root CGI console handler passes attacker-controlled input from the sh parameter to popen() without sanitization. An unauthenticated remote attacker can submit a crafted HTTP GET request to execute arbitrary commands with root privileges, with command output returned in the HTTP response. Successful exploitation permits full system compromise. The product line reached end of software support in March 2026.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises the confidentiality, integrity, and availability of the affected controller. Root-level command execution permits access to sensitive device data, modification of accounts and configurations, and disruption of controller services. Unauthorized control of a refrigeration supervisory system could also enable manipulation of monitoring, alarms, or refrigeration settings; these are potential consequences rather than confirmed outcomes of exploitation of this CVE.

Mitigation

If you can’t patch tonight, do this now.

Remove direct public access to controller management interfaces, including exposure through NAT and port forwarding. Isolate controllers in dedicated OT segments with restrictive firewall rules, and permit administration only from authorized systems through an MFA-protected VPN and a dedicated bastion. If using an authentication-enforcing reverse proxy, prevent direct access that bypasses it. Review HTTP and network logs for suspicious console requests, inspect exposed devices for unauthorized accounts and configuration changes, and compare configurations against known-good backups. Maintain independent temperature alarms while unsupported controllers remain operational. Password changes alone do not prevent this unauthenticated vulnerability.

Remediation

Patch, then assume compromise.

Upgrade devices running firmware earlier than 5.6.2 to version 5.6.2 or later to address this vulnerability's stated affected range. This does not resolve all known XWEB EVO vulnerabilities: the product line reached end of software support on March 16, 2026, and additional vulnerabilities affect later firmware without planned vendor fixes. Migrate to a supported replacement, such as XWEB Pro, and maintain its current security updates.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
CVE-2026-124002-POCStandalone exploit and comparative lab repository containing 48 files: a Python exploit client, Docker Compose definition, MIT license, README, eight evidence transcripts, and two parallel 18-file lab trees. The 29 code/build/web files comprise Python, C, Lua, shell, HTML, and Dockerfiles. Each lab implements a Python CGI server, Lua authentication/configuration endpoints, account fixtures, a web fingerprint page, shell/Lua password helpers, and compiled wlua/xwconsole helpers. It is a behavioral reimplementation, not supplied vendor firmware. poc.py offers six modes: check, inject, password, backdoor, rootexec, and config. Username input reaches shell-based find commands before authentication; hashed-account passwords reach an unquoted hashpass invocation. Injection modes write a temporary Lua payload and invoke wlua to attempt root execution, then retrieve proof files over HTTP. The privilege-escalation dependency is labeled CVE-2026-124003 in addition to the five headline CVEs. Backdoor mode requests an Administrator application session using xwebevonewgeneration; application user id 0 is not itself proof of OS-root execution. The console CGI passes the sh parameter to popen() after setuid(0). Configuration mode overwrites a fixed JSON configuration path and demonstrates an invalid-configuration state; this alone does not demonstrate root execution or arbitrary-path writes. The control tree removes setuid permissions and the master-password branch, adds credential allowlists, and gates configuration writes and console access on Administrator sessions. It is a custom negative control, not an independently validated vendor patch. Evidence transcripts report root output, configuration read-back/restoration, and rejected control attempts. No C2, reverse shell, or external exfiltration destination appears in the shown code. Important reliability limitations remain. README.md and poc.py are truncated in the supplied material, and no execution or external advisory validation was performed. The control wlua.c omits sys/wait.h while using WEXITSTATUS, potentially preventing its shown Debian build. Both xwpasswd helpers use bitwise syntax unsupported by the installed Lua 5.1. Comments asserting that Linux categorically ignores an interpreter binary's setuid bit during shebang execution are inaccurate, so the claimed initial www-data-to-root boundary should not be accepted without runtime verification. The control's configuration-content check merely searches for a model field rather than parsing JSON, and the HTTP server does not forward incoming Cookie headers into HTTP_COOKIE. These inconsistencies limit confidence in exact reproducibility but do not negate the plainly implemented injection and missing-authorization primitives. Product ranges, disclosure dates, exploitation claims, and CVE associations are repository assertions, not independently confirmed findings. Repository URL, revision, and archive size were not supplied; empty strings and zero represent unavailable metadata.fixedbyreboot · Disclosed Nov 14, 2026 · python · c · web · localOperational
FAQ

Frequently asked questions

Is CVE-2026-124010 exploited in the wild?
Yes. As of Nov 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2026-124010?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-124010, the earliest disclosed Nov 14, 2026.
Is there a patch for CVE-2026-124010?
Upgrade devices running firmware earlier than 5.6.2 to version 5.6.2 or later to address this vulnerability's stated affected range. This does not resolve all known XWEB EVO vulnerabilities: the product line reached end of software support on March 16, 2026, and additional vulnerabilities affect later firmware without planned vendor fixes.
How severe is CVE-2026-124010?
CVE-2026-124010 has a CVSS v4 score of 9.3 (Critical) and an EPSS score of 3.1% (88th percentile) as of Nov 16, 2026.
Activity feed

Recent activity

16 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
security weekNews · Nov 16, 2026Hackers Probe Newly Disclosed Flaws in Copeland Refrigeration Controllers - SecurityWeekAn unauthenticated root command execution vulnerability in Copeland/Dixell XWEB EVO refrigeration controllers running firmware predating the 2021 rewrite. Sensors observed four probes from one IP address on November 13. The activity was characterized as opportunistic exploitation activity, not evidence of involvement in the earlier refrigeration sabotage campaign attributed to Iran. Successful compromise of production devices was not reported.Read more ↗risky biz rssNews · Nov 16, 2026Risky Bulletin: Hackers accessed Barracuda's cloudOne of two actively exploited vulnerabilities in Copeland XWEB EVO refrigeration systems, collectively enabling unauthenticated OS command execution or modification of existing files. The content does not map each capability to an individual CVE. Attacks began two hours after disclosure; no patches were released because the product line had reached end-of-support.Read more ↗cyberveilleNews · Nov 15, 202614 vulnérabilités critiques dans Copeland XWEB EVO dont 2 exploitées activement | CyberVeilleUnauthenticated root command execution through the sh parameter of xwconsole.cgi in legacy, pre-2021 builds. The article reports four exploitation requests from an opportunistic scanner, including a request executing id.Read more ↗sh3llc0d3 blogNews · Nov 14, 2026VulnCheck Discloses 14 Unpatched Copeland XWEB | ShellcodeOne of 14 high- or critical-severity vulnerabilities reported in Copeland XWEB EVO. The article provides no individual technical description or affected version range for this CVE. No patch will be issued because the product is end-of-service; network isolation and hardware replacement are recommended.Read more ↗
+4 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity8Community discussion across Reddit, Mastodon, and other social sources.