CVE-2025-52547: Copeland LP E3 Supervisory Control · Improper Input Validation
Affects Copeland LP E3 Supervisory ControlSource CVE Database V5
Not known to be exploited · CVSS 8.7 High.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Sep 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Copeland LP E3 Supervisory Control | Affected
| Fixed in– |
AI-suggested
To mitigate this vulnerability effectively, European organizations should: 1) Immediately identify and inventory all instances of Copeland LP E3 Supervisory Control systems running firmware versions earlier than 2.31F01. 2) Implement network segmentation and strict access controls to isolate the supervisory control system from untrusted networks, limiting exposure to potential attackers. 3) Employ intrusion detection and prevention systems (IDPS) to monitor for anomalous API calls or repeated service crashes indicative of exploitation attempts. 4) Engage with Copeland LP and authorized vendors to obtain and apply firmware updates or patches as soon as they become available. 5) If patches are not yet available, consider deploying temporary compensating controls such as rate limiting API requests, implementing application-layer firewalls, or disabling vulnerable API endpoints if feasible without disrupting operations. 6) Conduct regular backups and develop incident response plans tailored to potential denial-of-service scenarios affecting supervisory control systems. 7) Train operational technology (OT) and cybersecurity teams to recognize and respond to signs of exploitation. 8) Collaborate with national cybersecurity agencies and industry information sharing groups to stay informed about emerging threats and mitigation strategies related to this vulnerability.
Description
E3 Site Supervisor Control (firmware version < 2.31F01) MGW contains an API call that lacks input validation. An attacker can use this command to continuously crash the application services.