CVE
Copeland XWEB EVO authentication bypass via hardcoded admin password
Affects Copeland XWEB EVO versions before 5.6.2, which contain a hardcoded Administrator password. Fixed in 5.6.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 5.6.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 5.6.2.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.76% · 55th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Copeland XWEB EVO application contains a hardcoded backdoor administrator password. An attacker on the network can log in without any credentials, using that built-in password, and gain full administrative control of the application.
Read the original description
XWEB EVO before 5.6.2 contains a hardcoded backdoor password vulnerability that allows unauthenticated remote attackers to gain full administrative access to the built-in Administrator account. Attackers can authenticate using the hardcoded credential xwebevonewgeneration in a single request to obtain a complete admin session and full control over the application. This product line reached it's end of service date in March 2026.
Who should check
Teams running Copeland XWEB EVO controllers before 5.6.2, including end-of-service units from the March 2026 product line
Read the source excerpt
“XWEB EVO before 5.6.2 contains a hardcoded backdoor password vulnerability”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.3/10CVSS 9.3
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 5.6.2.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-124004 (Dixell/Copeland XWEB EVO Hardcoded Administrator Backdoor Password), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-124004 (entry last updated 2026-11-12):
Affected:
- Copeland XWEB EVO: fixed in 5.6.2
Fixed versions: 5.6.2.
Conditions (all must be true for the bug to be hit):
- XWEB EVO versions before 5.6.2 (source: https://www.vulncheck.com/advisories/dixell-copeland-xweb-evo-hardcoded-administrator-backdoor-password)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-124004 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-124004 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://webapps.copeland.com/dixell/Content/Pages/AdvertisingMaterials/ProductNews/XWEB%20EVO%20EoS%20-%20Product_Bulletin_March_2026.pdf
- https://webapps.copeland.com/Dixell/Pages/SystemSoftwareUpdate
- https://www.vulncheck.com/advisories/dixell-copeland-xweb-evo-hardcoded-administrator-backdoor-password
- https://www.vulncheck.com/advisories/dixell-copeland-xweb-hardcoded-administrator-backdoor-password
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-124004
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-124004"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- Record last updated
Affected versions
- Copeland XWEB EVO
fixed in 5.6.2
Evidence 6
Vendor advisory · 2
Establishes: Affected and fixed versions.
- Advisory
- Patch
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-124004
Is CVE-2026-124004 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The product ships with a built-in Administrator account that uses a hardcoded password. Unauthenticated remote attackers can log in with that credential and get a full administrative session with full control over the application.Source: vulncheck.com
Which versions are affected by CVE-2026-124004?
XWEB EVO: before 5.6.2.Source: cve.now feed data
Am I affected, and how do I check?
XWEB EVO versions before 5.6.2 are listed as affected. To check an installation, compare its installed XWEB EVO version against 5.6.2.Source: vulncheck.com
How do I fix CVE-2026-124004?
Upgrade XWEB EVO to version 5.6.2, which is the listed fixed version.Source: vulncheck.com