Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2026-124007: Pre-authentication root command injection in XWEB EVO password processing

Published Nov 12, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days8 mentions · peak 4 in a dayToday
CVSS9.2Critical · v4
EPSS2.1%82nd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-124007CWE-78 · Improper Neutralization of Special…

CVE-2026-124007 is a pre-authentication operating-system command injection vulnerability in Copeland/Dixell XWEB EVO versions before 5.6.2. For accounts using hashed-password mode, the login, cleanup, and API handlers interpolate the supplied password into a hashpass command invocation without escaping shell metacharacters. An unauthenticated remote attacker can supply a crafted password to execute arbitrary operating-system commands, achieving root-level execution through the setuid-root wlua interpreter.

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 permits complete compromise of the affected controller, with high confidentiality, integrity, and availability impacts. Root-level command execution enables access to sensitive information, modification of controller configuration and software, and disruption of refrigeration monitoring or supervisory functions. Manipulation of refrigeration settings and alarms is a potential consequence of controller takeover, not an established observed outcome of this vulnerability.

Mitigation

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

Remove public internet exposure and restrict management access to segmented OT networks through an MFA-protected VPN or bastion. Limit controller access to explicitly authorized systems. While unsupported equipment remains operational, use independent temperature monitoring and out-of-band alarms to reduce operational consequences of controller compromise.

Remediation

Patch, then assume compromise.

Upgrade to XWEB EVO 5.6.2 or later to address this specific vulnerability. This does not resolve all separately identified XWEB EVO vulnerabilities. Because the product line reached end of software support in March 2026, plan migration to supported equipment rather than relying on a firmware upgrade as a complete long-term remediation.

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-124007 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-124007 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-124007?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-124007, the earliest disclosed Nov 14, 2026.
Is there a patch for CVE-2026-124007?
Upgrade to XWEB EVO 5.6.2 or later to address this specific vulnerability. This does not resolve all separately identified XWEB EVO vulnerabilities.
How severe is CVE-2026-124007?
CVE-2026-124007 has a CVSS v4 score of 9.2 (Critical) and an EPSS score of 2.1% (82nd percentile) as of Nov 17, 2026.
Activity feed

Recent activity

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

View more in app →
chocapikkNews · Nov 17, 2026Code of the Day: Unauthenticated Root in Copeland XWEB EVO - Chocapikk's Cybersecurity BlogOS command injection through the login.lua password field for hashed-mode accounts. On legacy firmware, command execution can be elevated to root through the setuid-root wlua interpreter. The report states that all 14 findings were demonstrated to root in laboratory testing. The flaw was removed in the 2021 rewrite, and no in-the-wild hits were reported.Read more ↗cyberveilleNews · Nov 15, 202614 vulnérabilités critiques dans Copeland XWEB EVO dont 2 exploitées activement | CyberVeilleCommand injection through the login.lua password field for accounts using hashed-password mode in legacy builds.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 ↗vulncheck blogNews · Nov 13, 2026Code of the Day: Unauthenticated Root in Copeland XWEB EVO | Blog | VulnCheckCommand injection in the legacy login password-processing path for hashed-mode accounts. The article reports laboratory reproduction and explains that legacy Lua command-injection paths can be chained with the setuid-root interpreter to obtain root execution. This implementation was removed in the 2021 rewrite.Read more ↗
+2 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 activity2Community discussion across Reddit, Mastodon, and other social sources.