VulnerabilityPublished 27 Feb 2026Updated 2 Mar 2026

CVE-2026-25085: Copeland XWEB 300D PRO · CWE-394

Affects Copeland XWEB 300D PROSource CVE Database V5

Compare

Not known to be exploited · CVSS 8.6 High.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

8.6High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
CopelandCopeland XWEB 300D PRO	Affected <=1.12.1	Fixed in–
CopelandCopeland XWEB 500D PRO	Affected <=1.12.1	Fixed in–
CopelandCopeland XWEB 500B PRO	Affected <=1.12.1	Fixed in–

AI-suggested

Immediately isolate Copeland XWEB 300D PRO devices from untrusted networks, ensuring they are accessible only from secure, internal management networks.
Implement strict network segmentation and firewall rules to restrict access to the device management interfaces.
Employ strong monitoring and logging of authentication attempts and device access to detect anomalous or unauthorized activities promptly.
Use VPNs or other secure remote access methods with multi-factor authentication for legitimate remote management to reduce exposure.
Regularly audit device configurations and access controls to ensure no unauthorized changes have occurred.
Engage with Copeland or authorized vendors to obtain information on forthcoming patches or firmware updates addressing this vulnerability.
Until patches are available, consider deploying intrusion detection/prevention systems (IDS/IPS) tuned to detect suspicious authentication bypass attempts targeting these devices.
Educate operational technology (OT) and IT teams about this vulnerability and the importance of rapid incident response if exploitation is suspected.
Maintain an inventory of all affected devices and prioritize remediation efforts based on criticality and exposure.
Plan for timely patch deployment once updates are released, including testing in controlled environments to avoid operational disruptions.

Description

A vulnerability exists in Copeland XWEB Pro version 1.12.1 and prior, in which an unexpected return value from the authentication routine is later on processed as a legitimate value, resulting in an authentication bypass.

Impact

The primary impact of CVE-2026-25085 is unauthorized access to Copeland XWEB 300D PRO devices, leading to a full breach of confidentiality. Attackers can bypass authentication without credentials, potentially gaining control over device management interfaces. This unauthorized access can result in exposure of sensitive configuration data, manipulation of device settings, and disruption of operational processes. In industrial or building automation contexts, such disruptions could affect HVAC systems, energy management, or other critical infrastructure components, leading to operational downtime or safety risks. The partial impact on integrity and availability means attackers might alter device behavior or cause service interruptions, though the main concern remains unauthorized access. The ease of remote exploitation without authentication or user interaction increases the likelihood of attacks, especially if devices are exposed to untrusted networks. Organizations worldwide using these devices face risks of espionage, sabotage, or operational disruption. The absence of known exploits currently offers a window for proactive defense, but the high CVSS score underscores the urgency of addressing the vulnerability.

CWE-394Unexpected Status Code or Return Value (opens in a new tab)
Base weaknessOWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product does not properly check when a function or operation returns a value that is legitimate for the function, but is not expected by the product.
OWASP Cheat Sheets
Logging (opens in a new tab)
Error Handling (opens in a new tab)
OWASP ASVS 4.0.3
V11.1.7 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Mar 2026, 21:31 UTC

WeaknessesCWE-394

Technical details

References

Community reviews

Related threats