On this page (7 sections)
A high-severity flaw, CVE-2026-124014, has been published for XWEB EVO versions 4.3.0 through 5.8.8. According to the GitHub Advisory Database entry, a remote attacker who can reach the device can rewrite its system configuration file without logging in, leading to configuration tampering and denial of service.
The product line reached its end of service date in March 2026, and the advisory does not list a patched version. Anyone running an XWEB EVO unit, especially one reachable from the internet or a flat internal network, should treat this as an exposure problem to manage rather than a simple update.
What happened
The advisory describes an unauthenticated arbitrary file write in XWEB EVO. A crafted POST request to config.lua with action=set performs no session validation and writes the raw, unvalidated request body to the system configuration file /etc/xwebconfig.json. The same endpoint also accepts unauthenticated action=get requests.
The record was published on November 12, 2026 by the National Vulnerability Database and mirrored the same day in the GitHub Advisory Database. The advisory is marked unreviewed there, and the NVD text is the same description, so this is effectively one source rather than two independent confirmations. The advisory also references a VulnCheck advisory, which we did not have the text of.
Technical details
The weakness class is missing authentication on a critical function (CWE-306). In plain terms, the configuration endpoint does not check whether the caller is logged in, and it does not check what is being written. Anyone who can send an HTTP request to the device can both read and replace its settings.
Per the advisory, an attacker can alter values such as the model and plugin fields, or push the device into a SYSTEM_NOT_CONFIGURED state. The stated outcomes are configuration tampering and denial of service. The CVSS v4 metrics list network attack vector, low complexity, no privileges, no user interaction, and high impact to integrity and availability, with no confidentiality impact on the vulnerable system.
Who is affected
Affected: XWEB EVO 4.3.0 through 5.8.8. Because the product reached end of service in March 2026 according to the advisory and a Copeland product bulletin it references, owners should not expect a routine fix. Check the vendor's system software update page and the end-of-service bulletin for current guidance, as we could not confirm what they offer.
The realistic risk is highest for units whose web interface is exposed to the internet, reachable through port forwarding, or sitting on a shared network with untrusted devices. Units only reachable from a tightly restricted management network face much lower risk.
How to check your exposure
- Inventory every XWEB EVO unit and note its firmware version in the device interface or your asset records. Versions 4.3.0 through 5.8.8 are in scope.
- Check your router and firewall rules for forwarded ports or public addresses that lead to the device web interface.
- Review web server or proxy logs, if any sit in front of the device, for unexpected POST requests to config.lua.
If you run a reverse proxy or log collector in front of the device, this read-only search shows requests to the affected endpoint. Run it on the log host and look for POST lines from addresses you do not recognize. Adjust the log path to your setup.
grep 'config.lua' /var/log/nginx/access.logIf you want to see what is reachable from outside, the Webforta Scan runs read-only scans of websites you verify, and the free SSL checker can show what a public address presents. Neither is a test for this specific flaw.
What to do now
No fixed version is documented, so the priority is to remove network access for untrusted parties and plan the device's replacement or migration.
- Identify all XWEB EVO units running 4.3.0 through 5.8.8.
- Remove any direct internet exposure, including port forwards and public IP mappings.
- Restrict access to the device to a dedicated management network or VPN, and allow only specific admin addresses through the firewall.
- Back up the current /etc/xwebconfig.json (or the device's exported configuration) so you can spot and reverse tampering.
- Contact the vendor or check its update page and end-of-service bulletin for supported replacements or mitigations.
- Plan replacement of end-of-service units and set a date for it.
- Watch for unexpected configuration changes or a SYSTEM_NOT_CONFIGURED state and treat them as a possible incident.
Detection and monitoring
Since the attack needs only network reachability, monitoring should focus on who can reach the device and whether its configuration changes. Keep a known-good copy of the configuration and compare it on a schedule. Alert on devices that drop offline or report an unconfigured state, as these match the denial-of-service outcome described.
Log POST requests to the device or its proxy, and alert on any from outside your management range. For public-facing hostnames in front of such equipment, Webforta Monitor can track uptime and certificate or DNS changes, which helps notice unexpected outages. For background on network filtering, see what a WAF is.
Open questions
- No patched version is listed, and the advisory shows affected and patched versions as unknown in its package fields.
- No exploitation in the wild is reported in the research we have, but that is absence of evidence rather than confirmation.
- Only one underlying description exists so far; the vendor's own statement on this CVE was not available to us.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
