On this page (7 sections)
CVE-2026-124004 describes a hardcoded backdoor password in XWEB EVO versions before 5.6.2. According to the GitHub Advisory Database entry, an unauthenticated remote attacker can log in to the built-in Administrator account with a fixed credential, in a single request, and obtain a complete admin session.
Anyone who runs an XWEB EVO web interface, especially one reachable from the internet or from a shared network, should treat this as urgent. The advisory also notes that this product line reached its end of service date in March 2026, which complicates patching.
What happened
The advisory was published on November 12, 2026 and describes a credential hardcoded into the software for the built-in Administrator account. A hardcoded credential is not a secret in practice: anyone who learns it can try it against any exposed instance running an affected version. According to the CVSS v4 metrics in the advisory, exploitation needs no user interaction, no privileges and no special attack requirements.
We are deliberately not repeating the credential here. The advisory publishes it, but there is no defensive value in spreading it further.
Technical details
This is a classic hardcoded credential flaw, tracked as CWE-798. Normally an administrator account gets a password set during installation or first login, and each device or server ends up with a different one. Here, the description says the software contains a fixed password for the built-in Administrator account, which behaves like a master key that is not tied to anything the owner configured.
The CVSS v4 metrics listed in the advisory are: network attack vector, low attack complexity, no attack requirements, no privileges required and no user interaction. Confidentiality, integrity and availability impact on the vulnerable system are all rated high. In plain terms, a remote attacker who can reach the login endpoint gets full control of the application.
Who is affected
Any deployment running XWEB EVO before 5.6.2 is in scope. The risk depends mostly on reachability:
- Interfaces exposed directly to the internet, including through port forwarding, are the most urgent.
- Interfaces reachable from a corporate, guest or vendor network can be abused by anyone on those networks.
- Interfaces reachable only through a VPN or an isolated management network have lower exposure, but still face anyone who gets onto that network.
The end of service point matters too. The advisory states the product line reached end of service in March 2026. It does not say whether a fix is offered to all users of that line, or how to obtain it. The advisory references a vendor software update page and an end of service product bulletin. Check both for current guidance.
How to check your exposure
- Find every XWEB EVO instance you operate, including ones installed by contractors or inherited from older projects.
- Open each instance's about or system information page, or ask your integrator, and note the installed version. Anything before 5.6.2 is affected.
- Determine whether the web interface is reachable from the internet. Test from outside your network, or review firewall and router port forwarding rules.
- Review the interface's login and audit history, if available, for Administrator sign-ins you do not recognize, especially from unfamiliar IP addresses.
- Check for unexpected changes to users, settings or connected devices.
Exposed management interfaces are a common weak point in small estates generally. Our small business website security guide covers inventorying and limiting what is reachable from the internet.
What to do now
- Confirm with the vendor that XWEB EVO 5.6.2 or later is available for your deployment (the advisory lists patched versions as unknown), then update through the vendor's official channel.
- If you cannot update, remove the web interface from the internet immediately and block inbound access at the firewall or router.
- Restrict access to a VPN or a small allowlist of management IP addresses.
- Place the system on a separate network segment away from general office and guest traffic.
- Review accounts, settings and connected devices for changes you did not make, and restore from a known-good backup if you find any.
- Rotate any credentials, API keys or integration secrets stored in or used by the application if you suspect it was accessed.
- Contact the vendor or your integrator about support options, since the product line is end of service, and plan a replacement if no fix is available for your version.
Detection and monitoring
Because the attack is a normal-looking login to a real account, there may be no obvious exploit signature. Focus on behavior:
- Alert on Administrator logins from addresses outside your management ranges.
- Watch web server and reverse proxy logs for repeated requests to the login endpoint from unknown sources.
- Monitor for new users, changed settings and outbound connections from the host that you cannot explain.
- Keep an inventory of internet-facing services and re-check it regularly, since a device that was private last quarter may be exposed after a network change.
For public-facing sites on your estate, Webforta Monitor can alert you to uptime, certificate, DNS and header changes, which helps spot unexpected changes on externally visible systems. It will not tell you whether an XWEB EVO login has been abused, so keep the application's own logs in scope.
What we do not know yet
- Whether the flaw is being exploited. The research does not report exploitation, and the CVE has no CISA KEV entry.
- Which exact versions before 5.6.2 are affected. The advisory lists affected and patched versions as unknown.
- Whether 5.6.2 is available to all customers given the end of service status.
- How the finding was discovered. Only the advisory text and its references are available to us so far.
Only one independent publisher covers this story so far, and the NVD entry repeats the same description. We will update this article if more details are published. Until then, assume any reachable instance running a version before 5.6.2 could be taken over by anyone who knows the advisory.
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.
