Actively exploited CVSS 9.3 Security news
Copeland XWEB EVO (CVE-2026-124010): 14 flaws in refrigeration controllers, two already exploited and no fix coming
On 12 and 13 November 2026 VulnCheck disclosed 14 vulnerabilities in Copeland (formerly Dixell) XWEB EVO, a controller that supermarkets and warehouses use to monitor and manage refrigerated cases and cold rooms remotely. Attackers started probing two of the flaws within hours. Copeland ended support for the product line in March 2026, so there will be no patches. Here is who is affected, how to spot attempts and what to do.
Key points
- VulnCheck disclosed 14 vulnerabilities (CVE-2026-124002 to CVE-2026-124015) in Copeland/Dixell XWEB EVO refrigeration controllers. They were found by researcher Valentin Lobstein.
- The most severe, CVE-2026-124010 (CVSS 4.0 9.3), lets an unauthenticated attacker run commands as root through the xwconsole.cgi script in versions before 5.6.2. CVE-2026-124014 (CVSS 4.0 8.8) lets an unauthenticated attacker overwrite the configuration in versions 4.3.0 through 5.8.8.
- VulnCheck's honeypots caught exploitation attempts against CVE-2026-124014 less than two hours after the CVE record went live on 12 November, and against CVE-2026-124010 early on 13 November.
- Copeland ended support for XWEB EVO in March 2026; neither VulnCheck nor NVD lists a fixed version. The only defences are taking the device off the internet, a VPN, and replacement.
- VulnCheck counts roughly 1,700 to 2,000 XWEB EVO units visible on the internet. XWEB controllers were among the devices hit in the October wave of attacks on refrigeration systems in France.
Vulnerabilities: CVE-2026-124010, CVE-2026-124014
What happened
VulnCheck has disclosed 14 vulnerabilities in XWEB EVO refrigeration controllers. The product was originally made by the Italian firm Dixell and is now sold by Copeland. Supermarkets, warehouses and other sites use it to monitor and adjust refrigerated cases, cold rooms and freezers remotely. The CVE records (CVE-2026-124002 to CVE-2026-124015) went live on 12 November 2026 and the full write-up followed on 13 November. The flaws were found by researcher Valentin Lobstein.
Attackers moved on two of them almost immediately. VulnCheck's honeypots saw the first attempt against CVE-2026-124014 at 22:00 UTC on 12 November, less than two hours after the NVD record was published, and the first attempt against CVE-2026-124010 at 03:41 UTC on 13 November. VulnCheck added both to its own known-exploited catalogue (VulnCheck KEV). As of 16 November, the NVD records do not show either flaw in CISA's KEV catalogue.
The bad news is that no fixes are coming. Copeland ended software support for XWEB EVO in March 2026, and neither VulnCheck nor NVD lists a patched version.
Technical details
According to VulnCheck and the NVD records:
- CVE-2026-124010 (CVSS 4.0 9.3, CVSS 3.1 9.8) – the web script
xwconsole.cgiruns with root privileges and passes the value of itsshparameter, unsanitised, to be executed as a system command. An attacker can therefore run any command as root without logging in. It affects versions before 5.6.2. - CVE-2026-124014 (CVSS 4.0 8.8, CVSS 3.1 9.1) – the
config.luascript accepts a POST request withaction=setwithout checking for a session and overwrites the configuration file/etc/xwebconfig.json. An attacker can tamper with settings or force the controller into a "not configured" state, effectively taking it out of service. It affects versions 4.3.0 through 5.8.8, which includes the last release. - The other 12 flaws, per VulnCheck, include command injection on the login page and elsewhere in the interface, a hardcoded administrator password, a predictable daily password derived from the MAC address and date, an operating-system root password derived from that daily code, an information leak, and a password reset that skips session checks. Some affect older builds (VulnCheck tested 5.2.3), others the final 5.8.8 release too. VulnCheck has not seen exploitation of these 12.
So far VulnCheck has seen only four attempts against CVE-2026-124010, all running the harmless id command – a typical check for whether a device responds. CVE-2026-124014 drew 125 attempts in under nine hours from a single address. VulnCheck does not tie either address to a known group or to the October refrigeration attacks in France.
Who is affected
Anyone running refrigeration with an XWEB EVO controller (VulnCheck names the XWEB 300D EVO, 500D EVO and 500 EVO), particularly where the web interface is reachable from the internet. VulnCheck counts about 1,663 such units on Shodan and about 1,960 on Onyphe. The older XWEB Pro line is not covered by this disclosure; it has its own flaws, fixed earlier and described in CISA advisory ICSA-26-057-10.
XWEB controllers were among the devices hit in the wave of attacks on refrigeration systems in Europe. On 13 October 2026, France's CERT-FR reported compromised Copeland and Dixell XWEB units, alongside Danfoss controllers. Commercial refrigeration is often managed by a service contractor; if you don't know which controller you have or how it is connected, ask them.
How to tell if you were compromised
Indicators from VulnCheck's write-up:
Source IPs of exploitation attempts (12–13 Nov 2026):
202.61.138.117 (AS152194) – attempts against CVE-2026-124014
177.4.12.11 (AS140227) – attempts against CVE-2026-124010
Suspicious requests in web interface logs:
Unauthenticated POST to config.lua (especially with action=set)
GET to /cgi-bin/xwconsole.cgi with an sh parameter
File modified by the attack:
/etc/xwebconfig.json
What to check:
- internet exposure – try opening the interface from outside your network, for example from a phone on mobile data,
- firewall, VPN or reverse proxy logs in front of the controller – requests to
config.luaandxwconsole.cgifrom unknown addresses, - the controller's configuration and status – changed settings, a "not configured" state, unexpected restarts,
- temperatures and defrost schedules – for compromised controllers CERT-FR recommends reviewing the whole configuration, not just temperature set points.
Our IOC extractor pulls addresses and other indicators out of logs, and the CVSS calculator breaks down the scores. Both run entirely in your browser.
What to do
- Take the XWEB EVO web interface off the internet. It is the only effective defence – both exploited flaws work without authentication, so passwords don't help.
- Allow remote access only through a VPN you control, including for your service contractor. CERT-FR considers allow-listing the contractor's IP addresses a temporary measure only.
- If the controller was internet-facing, assume it may have been tampered with. Review its configuration, account passwords and access logs. CERT-FR notes that a factory reset removes an attacker's changes but leaves the device vulnerable, so only put it back into service once it is no longer reachable from the internet.
- Plan a replacement with a supported system. Copeland has not supported XWEB EVO since March 2026, and VulnCheck says the vendor will not fix the flaws in the final release under its own policy.
Timeline
- March 2026 – Copeland ends software support for the XWEB EVO line.
- 12–13 Oct 2026 – CERT-FR warns of attacks on remotely managed refrigeration in France, including Copeland and Dixell XWEB controllers.
- 17 Oct 2026 – VulnCheck reports its findings to Copeland PSIRT.
- 12 Nov 2026, 20:18 UTC – the CVE records are published in NVD; the first attempt against CVE-2026-124014 follows at 22:00 UTC.
- 13 Nov 2026 – first attempt against CVE-2026-124010 at 03:41 UTC; VulnCheck publishes its full write-up.
We verified the flaws, affected versions and exploitation attempts in VulnCheck's write-up and advisories and in the NVD records. We could not read Copeland's end-of-support bulletin (PDF), so the March 2026 date comes from VulnCheck and NVD. We have not verified any attribution of the October French campaign in a primary source, so we do not include one.
Verified against sources on 16 November 2026.
FAQ
We have an XWEB unit but don't know if it's EVO or Pro. How do we tell?
The model is printed on the unit's label and shown in its web interface (for example XWEB 300D EVO or XWEB 500D PRO). This story is about the EVO line. XWEB Pro has its own, older set of flaws, fixed in firmware later than 1.12.1, covered in CISA advisory ICSA-26-057-10.
Is changing the password enough?
No. Both exploited flaws work without logging in at all, so a password does not help. Several of the other flaws involve hardcoded and predictable passwords that the owner cannot change. The only effective protection is making sure nobody on the internet can reach the interface.
The vendor won't ship a fix. What now?
Until you replace it, keep the controller on an internal network or behind a VPN you control, and give your service contractor access through that VPN. At the same time, plan a move to a supported system with the contractor. France's CERT-FR describes leaving an unsupported device reachable from the internet as a very high risk.
Who should I report an incident to?
In the US, report to CISA (cisa.gov/report); in the UK, to the NCSC. Elsewhere in Europe, contact your national CERT. Keep the controller's logs and any firewall or VPN logs before resetting the device.
Sources
- VulnCheck – Code of the Day: Unauthenticated Root in Copeland XWEB EVO (13 November 2026)
- VulnCheck – Advisory: XWEB EVO Unauthenticated Configuration Write via config.lua (CVE-2026-124014)
- VulnCheck – Advisory: XWEB EVO Unauthenticated Command Injection via xwconsole.cgi (CVE-2026-124010)
- NVD – CVE-2026-124010
- NVD – CVE-2026-124014
- CERT-FR – CERTFR-2026-ALE-012: attacks on remote management of refrigeration systems (in French)
- CISA – ICS advisory ICSA-26-057-10: Copeland XWEB and XWEB Pro
Spotted a mistake? Let us know and we will correct it openly.