CVE
Copeland XWEB EVO unauthenticated config overwrite in config.lua handler
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Do first: Apply the patch listed under Evidence.
- 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.73% · 54th 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
Copeland XWEB EVO (also listed as Dixell/Copeland XWEB EVO) has an unauthenticated flaw in its config.lua handler that lets a remote attacker, without logging in, overwrite the system configuration file with raw request data. This can alter settings such as model and plugin values or push the device into a not-configured state, causing configuration tampering and denial of service.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
XWEB EVO 4.3.0 through 5.8.8 contains an unauthenticated arbitrary file write vulnerability that allows remote attackers to modify the system configuration file /etc/xwebconfig.json by sending a crafted POST request to config.lua with action=set, which performs no session validation and writes the raw, unvalidated request body. Attackers can tamper with configuration values such as model and plugin fields or trigger a SYSTEM_NOT_CONFIGURED state via the unauthenticated action=get and action=set operations, resulting in configuration tampering and denial of service. This product line reached it's end of service date in March 2026.
Who should check
Teams running Copeland XWEB EVO controllers, versions 4.3.0 through 5.8.8. The product line reached end of service in March 2026.
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
- Severity8.8/10CVSS 8.8
- 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
Apply the patch listed under Evidence.
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-124014 (Dixell/Copeland XWEB EVO Unauthenticated Configuration Write via config.lua), 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-124014 (entry last updated 2026-11-12):
Affected:
- Copeland XWEB EVO: from 4.3.0, through 5.8.8
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Affects Copeland/Dixell XWEB EVO versions 4.3.0 through 5.8.8 (source: https://www.vulncheck.com/advisories/dixell-copeland-xweb-evo-unauthenticated-configuration-write-via-config-lua)
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-124014 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-124014 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-unauthenticated-configuration-write-via-config-lua
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-124014
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-124014"}.Timeline
- CVE published
- Record last updated
- First seen by cve.now
Affected versions
- Copeland XWEB EVO
From 4.3.0 · through 5.8.8
Evidence 5
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-124014
Is CVE-2026-124014 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?
An unauthenticated remote attacker can write arbitrary files on the XWEB EVO. The attacker can modify /etc/xwebconfig.json, tamper with values such as the model and plugin fields, or put the device into a SYSTEM_NOT_CONFIGURED state, which causes denial of service.Source: vulncheck.com
Which versions are affected by CVE-2026-124014?
XWEB EVO: from 4.3.0 through 5.8.8.Source: cve.now feed data
Am I affected, and how do I check?
The vulnerability affects Copeland/Dixell XWEB EVO versions 4.3.0 through 5.8.8. To check a device, compare its reported XWEB EVO firmware version with that range.Source: vulncheck.com
How do I fix CVE-2026-124014?
The checked facts do not list a fixed version or vendor patch identifiers, so no upgrade target can be given from them. Check the vendor's advisory for a fix.Source: vulncheck.com