CVE-2025-52545:
Privilege escalation vulnerability in Copeland LP E3 Site Supervisory Control firmware (< 2.31F01) where the RCI service API exposes usernames and password hashes due to insufficiently protected credentials, allowing network-based exploitation with low privileges and no user interaction (CVSS v4.0 base score 7.7, HIGH).
Score
A numerical rating that indicates how dangerous this vulnerability is.
7.5High- Published Date:Sep 2, 2025
- CISA KEV Date:*No Data*
- Industries Affected:20
Threat Predictions
- EPSS Score:0.1
- EPSS Percentile:16%
Exploitability
- Score:3.9
- Attack Vector:NETWORK
- Attack Complexity:LOW
- Privileges Required:NONE
- User Interaction:NONE
- Scope:UNCHANGED
Impact
- Score:3.6
- Confidentiality Impact:HIGH
- Integrity Impact:NONE
- Availability Impact:NONE
Description Preview
Privilege escalation vulnerability in Copeland LP E3 Site Supervisory Control firmware (< 2.31F01) where the RCI service API exposes usernames and password hashes due to insufficiently protected credentials, allowing network-based exploitation with low privileges and no user interaction (CVSS v4.0 base score 7.7, HIGH).
Overview
The issue is a credential protection weakness in the E3 Supervisory Controls’ RCI API that exposes user names and password hashes for the application services when queried, enabling privilege escalation over the network on firmware versions prior to 2.31F01. This vulnerability is categorized under CWE-522 and CAPEC-122, and is of high severity due to its potential impact on confidentiality, integrity, and availability. Affected deployments must consider network-level mitigations and timely firmware upgrades to remove exposure.
Remediation
- Upgrade firmware of all affected E3 Supervisory Controls to a version greater than 2.30F1 (preferably 2.31F01 or newer) to eliminate the credential exposure.
- If upgrading is not immediately feasible, implement strict network access controls to the RCI service: place the E3 device behind a firewall, restrict access to trusted VLANs/subnets, and ensure the management interface (ETH 0) is not reachable from untrusted networks.
- After remediation, rotate credentials exposed by the API (usernames and password hashes) and review access logs for anomalous activity; enforce strong password policies and consider hardening credential storage or hashing mechanisms as recommended by the vendor.
- Monitor for and apply any vendor-provided patches or advisories related to this vulnerability.
References
Industries Affected
Below is a list of industries most commonly impacted or potentially at risk based on intelligence.
