CVE-2025-57704VulnerabilityPublished 26 Aug 2025

CVE-2025-57704: Delta Electronics EIP Builder · XXE – Improper Restriction of XML External Entity Reference

Affects Delta Electronics EIP BuilderSource CVE Database V5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.5Medium

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

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

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

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

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-25.

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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC 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
Delta Electronics EIP Builder	Affected =0	Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should implement the following specific measures: 1) Restrict access to systems running EIP Builder to trusted personnel only, minimizing the risk of malicious XML files being introduced. 2) Educate users about the risks of opening untrusted XML files and implement strict policies to avoid processing files from unknown or unverified sources. 3) Employ application whitelisting and endpoint protection solutions that can detect and block suspicious file parsing activities or unusual XML processing behavior. 4) Monitor system logs and application behavior for any anomalous file access or XML parsing errors that could indicate exploitation attempts. 5) Coordinate with Delta Electronics to obtain security updates or patches as soon as they become available and plan for timely deployment. 6) Consider network segmentation to isolate systems running EIP Builder from broader enterprise networks to limit lateral movement in case of compromise. 7) If possible, configure XML parsers or the application environment to disable external entity processing or use safer XML parsing libraries that enforce strict entity resolution policies.

Description

Delta Electronics EIP Builder version 1.11 is vulnerable to a File Parsing XML External Entity Processing Information Disclosure Vulnerability.

Impact

For European organizations using Delta Electronics EIP Builder, this vulnerability poses a risk of sensitive information leakage from systems where the software is installed. Since the attack requires local access and user interaction, the threat vector is primarily through social engineering or insider threats where a malicious XML file is introduced and opened by a user. The confidentiality breach could expose intellectual property, configuration files, or other sensitive data relevant to industrial automation or control systems managed by EIP Builder. Given that Delta Electronics products are often used in industrial and manufacturing sectors, the impact could extend to operational technology environments, potentially undermining trust in system integrity and exposing critical infrastructure data. Although the vulnerability does not directly affect system integrity or availability, the information disclosure could facilitate further targeted attacks or espionage activities. European organizations with industrial automation deployments should be particularly vigilant, as such information leaks could have regulatory and compliance implications under GDPR and other data protection laws.

CWE-611Improper Restriction of XML External Entity Reference (opens in a new tab)
Base weaknessOWASP Top 10 A02:2025: Security Misconfiguration (opens in a new tab)
The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.
Implementation · System Configuration
Many XML parsers and validators can be configured to disable external entity expansion.
OWASP Cheat Sheets
Deserialization (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V5.5.2 (opens in a new tab)
Attack patterns
Data Serialization External Entities Blowup (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

filecenter.deltaww.com/news/download/doc/Delta-PCSA-2025-00013_EIP%20Builder%20XML%20External%20Entity%20Processing%20Information%20Disclosure%20Vulnerability.pdf (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Sep 2025, 01:15 UTC

WeaknessesCWE-611

Technical details

References

Community reviews

Related threats