Deception Check homeResearch blog

Cold-chain operations / XWEB EVO

Can you take XWEB EVO off the internet and keep the freezers cold?

Two flaws can give an attacker full privileges on a legacy refrigeration supervisor. Ask IT and your refrigeration contractor to trace the maintenance connection, close direct internet access, and verify cooling and alarms on site.

Start with one site and one contractor

XWEB EVO is Copeland and Dixell’s web-based supervisor for refrigeration equipment. It can monitor temperatures and alarms and, depending on the installation, let an operator change settings on connected equipment. Ask the contractor how they reach the login page today. IT can check that answer against the firewall, router, and remote access configuration, including any contractor-managed connection.

IT closes the public route

Check for a public address, port forwarding, or a router DMZ rule pointing at the unit. Remove direct access and verify from an approved connection outside the site. Limit contractor access to the required devices through a restricted VPN with named accounts and MFA at the gateway.

Facilities verifies cooling and alarms

Identify any alarm or monitoring service that depends on the existing link. Arrange an on-site check during the change and verify local cooling, temperatures independently of XWEB, and alarm delivery to the person on call. Coordinate the cutover with the contractor and check service and insurance obligations for any telemetry you plan to interrupt.

Copeland and Dixell’s security and recovery guide gives model-specific steps for isolating and checking units. CERT-FR’s refrigeration alert also calls for removing direct internet access and checking defrost settings before restoring protected maintenance access.

Two steps from a login request to root

On affected firmware, the login handler uses the submitted username in a shell command before checking the password. The initial command runs as the web service. In a lab built from vendor firmware, VulnCheck used a separate flaw in the privileged Lua interpreter to get root, the appliance’s highest level of access.

  1. STEP 1 / CVE-2026-124002Run a command as the web service

    The login handler uses the username in a command before checking the password.

    Web-service privileges
  2. STEP 2 / CVE-2026-124003Raise privileges on the supervisor

    A separate flaw in the privileged Lua interpreter lets code run as root.

    Root on the appliance
VulnCheck demonstrated this chain in a firmware lab running 5.2.3. A login request can start the chain without valid credentials. The CVE record for the separate root flaw lists versions before 5.6.2 as affected.

The CNA advisory lists XWEB EVO 5.2.3 through versions before 5.7.0 as affected by the username flaw. The CVE record lists 5.7.0 as unaffected by this specific flaw. Other findings reach firmware 5.8.8. Copeland ended software support for EVO on March 16, 2026. Confirm the last available firmware for your exact model with Copeland and plan migration to supported equipment. Keep both the existing and replacement management interfaces private. Copeland end-of-support bulletin

Compare three records from the same time window

Start with a site that had a public management route or an unexplained change. Record the unit, site, and time zone. Export what you already retain and account for any clock offset. If the unit or gateway never recorded a field, mark it unavailable.

01 / Firewall or VPN

Who could reach the supervisor?

Filter allowed connections and VPN sessions to the XWEB address, accounting for any old NAT rule. Record the source, translated destination, port, time, and VPN identity where available. Compare with the contractor’s authorized account and work window. Review unexpected outbound connections from the same unit against its normal destinations.

02 / HTTP or appliance

What reached the login route?

If an appliance or HTTP-aware proxy already retains request paths, look for unexpected requests to /cgi-bin/login.lua from those sources. Record the route, method, status, and time. An ordinary sign-in can use the same route and a response code cannot establish that a command ran. Keep credentials and full query strings out of shared notes. If host evidence is available through your response process, look for unexpected web-service child processes or execution by wlua in the same window. Treat those as leads and corroborate before claiming root access.

03 / Refrigeration and alarms

What changed at the site?

Use retained audit or change records if available. Compare current setpoints, defrost schedules, alarm thresholds and recipients, and user profiles with an approved baseline or known-good backup. Ask who authorized changes. Compare alarm and temperature trends with an independent logger or an on-site reading. Preserve timestamped records and configuration snapshots through your incident process.

A firewall flow can show a reachable destination, and an HTTP record can show a request. Establish execution with separate host evidence where available. Unexplained configuration or temperature changes still warrant a facilities and security response when host logs are missing.

Before you restore maintenance access

For a suspected compromise, isolate the management route and work with facilities, security, and the refrigeration contractor on recovery. Preserve evidence where doing so won’t delay containment. Use Copeland’s local recovery procedure and an approved pre-incident backup as appropriate. Before reopening protected access, have someone on site confirm temperatures, verify the authorized settings, and run an agreed alarm test with the person who receives alerts.

The Deception Check

Pick the first XWEB site. Name who closes the public route, who verifies cooling on site, and who can authorize reconnection. For a broader inventory of refrigeration and other vendor-managed systems, use Refrigeration is OT. Who is watching the controls?