On this page (7 sections)
CVE-2026-124010 describes a critical command injection flaw in XWEB EVO versions before 5.6.2. According to the GitHub Advisory Database entry, an unauthenticated remote attacker can run arbitrary commands as root through a setuid-root CGI program named xwconsole.cgi, which leads to full system compromise.
Anyone who runs an XWEB EVO device or web interface, or who manages networks where one is reachable, should treat this as urgent. The same advisory notes that this product line reached its end of service date in March 2026, which complicates the usual advice to simply wait for a vendor patch.
What happened
The flaw was published on November 12, 2026 and appears in both the NVD record and the GitHub Advisory Database. The NVD text repeats the GitHub description, so these are one set of claims rather than two independent confirmations. A VulnCheck advisory is listed as a reference, but its content was not part of the research for this article.
The GitHub entry is marked as unreviewed, and it lists affected and patched versions as unknown. The only version statement we can make with confidence is the one in the description: XWEB EVO before 5.6.2.
Technical details
The vulnerable component is xwconsole.cgi, a CGI program installed setuid-root. That means it runs with root privileges no matter which user or web process starts it. According to the advisory, the program takes input from a parameter named sh and passes it to the C library function popen() without sanitizing it. popen() starts a shell to run a command string, so any attacker-controlled text that reaches it can become a command.
Two weakness classes are attached to the record. CWE-78 covers the missing neutralization of special characters before they reach an operating system command. CWE-250 covers running code with more privilege than it needs. Combined, a simple input handling mistake becomes a direct path to root.
The CVSS v4 metrics shown on the advisory explain the 9.3 score: network attack vector, low attack complexity, no attack requirements, no privileges required, no user interaction, and high impact on confidentiality, integrity and availability of the vulnerable system. In plain terms, an attacker who can reach the interface over the network does not need an account or any help from a user.
Who is affected
- Operators of any XWEB EVO installation running a version before 5.6.2.
- Organizations that expose the XWEB EVO web interface to the internet, to a flat internal network, or to a partner or vendor network.
- Teams that cannot upgrade because the product line is past its March 2026 end of service date.
The research does not say which hardware models or deployment types ship with the vulnerable CGI, so check with the vendor rather than assuming that a particular device is safe. The vendor pages listed as references are the system software update page and the March 2026 end of service product bulletin. We did not have their contents, so confirm the fix and support details there.
How to check your exposure
- Build an inventory of XWEB EVO devices and note the firmware or software version shown in the device's own administration interface or documentation.
- Compare each version with 5.6.2. Anything older is in the affected range described by the advisory.
- Find out whether each device's web interface is reachable from the internet, from user networks or only from a dedicated management network.
- Review web server or reverse proxy logs, if you have them, for requests to a path containing xwconsole.cgi, and treat any request from an unexpected source as suspicious.
If you front these devices with an nginx reverse proxy or log collector, a read-only search like the one below shows whether anything has requested the vulnerable CGI. Run it on the proxy or log host and adjust the log path to your environment; this is a generic grep and not a vendor-supplied command.
grep -i "xwconsole.cgi" /var/log/nginx/access.log*Any hit is worth a closer look, particularly a request with a query string or body containing an sh parameter. A clean result does not prove the device is safe, since the device may not log requests at all.
What to do now
- Identify every XWEB EVO instance and its version, including ones that are rarely touched.
- Remove direct internet exposure today: place the interface behind a VPN or firewall rule that allows only named administrative addresses.
- Check the vendor's system software update page and upgrade to 5.6.2 or later where the update is available for your device.
- If your model is past end of service and has no fix, plan replacement and keep it isolated from other networks until then.
- If you can block it at a gateway or web application firewall, deny requests to xwconsole.cgi from untrusted sources as a temporary measure.
- Review logs and device behavior for signs of compromise, and if you suspect it, treat the device as fully controlled by an attacker and rebuild it from a known good state.
- Rotate any credentials, keys or tokens stored on or reachable from the device if compromise is possible.
The end of service status matters in practice. The advisory says the product line reached end of service in March 2026, so a patch for every model may not exist or may not keep coming. Ask the vendor directly which versions and hardware are still supported.
Detection and monitoring
Because a successful attack runs as root, signs of compromise can be broad: new user accounts, changed configuration, unexpected outbound connections, unfamiliar processes or scheduled jobs. If the device can export logs, send them to a separate system so an attacker cannot erase them.
- Alert on any access to the device's web interface from addresses outside your administrative range.
- Watch for new outbound connections from the device to the internet, since a compromised device may reach out to attacker infrastructure.
- Track certificate and DNS changes on hostnames that point at these devices; Webforta Monitor can watch for those changes on sites you verify.
- Run an outside-in check of what your public addresses expose with the Webforta scanner, and read what outside-in malware detection can and cannot see to understand its limits for embedded devices.
If you suspect a compromise, follow our guide on what to do when a website is hacked.
Timeline
| Date | Event |
|---|---|
| March 2026 | XWEB EVO product line reaches end of service, per the advisory text and a vendor product bulletin listed as a reference |
| November 12, 2026 | CVE-2026-124010 published to the NVD and the GitHub Advisory Database |
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.
