CVE-2025-25264VulnerabilityPublished 16 Jun 2025Updated 21 Nov 2025

CVE-2025-25264: WAGO CC100 0751-9x01 · Permissive Cross-domain Policy with Untrusted Domains

Affects WAGO CC100 0751-9x01Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.5Medium

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

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

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

Attack Vector: Network
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: 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: 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 16 Jun 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
WAGO CC100 0751-9x01	Affected =0.0.0	Fixed in–

AI-suggested

1. Immediately review and restrict the CORS policy on WAGO CC100 0751-9x01 devices to allow only trusted, necessary domains, ideally limiting to internal management interfaces or specific administrative domains. 2. Implement network segmentation to isolate industrial controllers from general internet access and reduce exposure to malicious websites. 3. Educate administrators and operators about the risks of visiting untrusted websites, emphasizing phishing awareness and social engineering defenses. 4. Monitor network traffic for unusual cross-origin requests or attempts to access device file systems remotely. 5. Engage with WAGO support or vendors for any forthcoming patches or firmware updates addressing this vulnerability. 6. Consider deploying web filtering or proxy solutions to block access to known malicious domains and reduce the risk of accidental visits to attacker-controlled sites. 7. Conduct regular security audits of industrial control systems to detect misconfigurations like overly permissive CORS policies. 8. If possible, implement multi-factor authentication and strict access controls on administrative interfaces to reduce the risk of unauthorized access.

Description

An unauthenticated remote attacker can trick an admin to visit a website containing malicious java script code. The current overly permissive CORS policy allows the attacker to obtain any files from the file system.

Impact

For European organizations, especially those in industrial automation, manufacturing, and critical infrastructure sectors, this vulnerability poses a risk of sensitive data exposure from WAGO CC100 0751-9x01 devices. Confidentiality breaches could lead to leakage of operational parameters, system configurations, or proprietary information, potentially aiding further attacks or industrial espionage. While the vulnerability does not directly impact system integrity or availability, the exposure of sensitive files could facilitate secondary attacks or disrupt trust in operational technology environments. The requirement for user interaction (admin visiting a malicious site) means that social engineering or phishing campaigns could be leveraged by attackers. Given the widespread use of WAGO controllers in European industrial sectors, the vulnerability could have significant operational security implications if exploited. The absence of known exploits in the wild reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits following public disclosure.

CWE-942Permissive Cross-domain Security Policy with Untrusted Domains (opens in a new tab)
Variant weaknessOWASP Top 10 A02:2025: Security Misconfiguration (opens in a new tab)
The product uses a web-client protection mechanism such as a Content Security Policy (CSP) or cross-domain policy file, but the policy includes untrusted domains with which the web client is allowed to communicate.
Architecture and Design · Operation · Attack Surface Reduction
Define a restrictive Content Security Policy or cross-domain policy file.
Architecture and Design · Operation · Attack Surface Reduction
Avoid using wildcards in the CSP / cross-domain policy file. Any domain matching the wildcard expression will be implicitly trusted, and can perform two-way interaction with the target server.
Architecture and Design · Operation · Environment Hardening
For Flash, modify crossdomain.xml to use meta-policy options such as 'master-only' or 'none' to reduce the possibility of an attacker planting extraneous cross-domain policy files on a server.
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V1.14.1 (opens in a new tab)
V13.4.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

certvde.com/en/advisories/VDE-2025-018/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Nov 2025, 12:26 UTC

WeaknessesCWE-942

Technical details

References

Community reviews

Related threats