cve.bz

CVE-2026-124011 Dixell/Copeland XWEB EVO Information Disclosure via sysinfo.lua

6.9 mediumEPSS 0.4%

Medium (6.9) in copeland xweb evo. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
XWEB EVO 5.6.2 through 5.8.8 contains an information disclosure vulnerability that allows unauthenticated attackers to obtain the device's eth0 MAC address and system clock by accessing sysinfo.lua, which also feeds the pre-login page. Attackers can use the disclosed MAC address and system clock values to offline derive the MAC-based daily password, enabling unauthorized authentication to the device. This product line reached it's end of service date in March 2026.

Severity

CVSS 4.0

6.9 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
0.4% estimated probability of exploitation activity in the next 30 days; 33rd percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-497 Exposure of Sensitive System Information to an Unauthorized Control Sphere
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
VulnCheck (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-124011 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-124011?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-124011?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-124011 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-124011

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-124011](https://cve.bz/cve/badge/CVE-2026-124011.svg)](https://cve.bz/cve/CVE-2026-124011)

HTML:

<a href="https://cve.bz/cve/CVE-2026-124011"><img src="https://cve.bz/cve/badge/CVE-2026-124011.svg" alt="CVE-2026-124011"></a>

Affected

  • copeland:xweb evo

Versions

From the CNA's record in the CVE List.

ProductAffected
Copeland XWEB EVOfrom 5.6.2 through 5.8.8

Attack patterns (CAPEC)

  • CAPEC-170 Web Application Fingerprinting Likelihood: High · Severity: Low
  • CAPEC-694 System Location Discovery Likelihood: High · Severity: Very Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON