dbcve.org
E3 Supervisory Controller FirmwareOperating system · Copeland

CVE-2025-52550

HIGH · 7.2 CVSS v3.1 Published 2025-09-02
Fix available
A fix is available. Upgrade to 2.31f01 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
E3 Site Supervisor Control (firmware version < 2.31F01) firmware upgrade packages are unsigned. An attacker can forge malicious firmware upgrade packages. An attacker with admin access to the application services can install a malicious firmware upgrade.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The E3 Site Supervisor Control firmware versions prior to 2.31F01 lack digital signature validation on upgrade packages. This allows an authenticated admin attacker to craft and install malicious firmware images, potentially achieving full device compromise.

MitigationUpgrade E3 Site Supervisor Control firmware to version 2.31F01 or later which implements signed firmware packages, and verify the signing chain in the update mechanism.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
E3 Supervisory Controller FirmwareOperating system
Affected:< 2.31f01

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed firmware version
    Access the E3 Site Supervisor Control web interface, CLI, or API and retrieve the current firmware version information. Look for a version field in the system status, about page, or device information section.
    Affected if The displayed version is less than 2.31F01 (for example, 2.30, 2.28, or any version number below 2.31f01).
  2. Confirm the device model is Copeland E3 Supervisory Controller
    Verify that the device is specifically the Copeland E3 Supervisory Controller by checking the device name, model number, or product identifier in the management interface.
    Affected if The device is a Copeland E3 Supervisory Controller and the firmware version is below 2.31F01.
  3. Check if firmware upgrade functionality is accessible
    Navigate to the firmware upgrade or software update section of the admin interface to confirm the upgrade feature exists and is accessible to an authenticated administrator.
    Affected if The upgrade feature is present and accessible to authenticated admin users, and the firmware version is below 2.31F01.
  4. Verify admin authentication is enabled
    Confirm that administrator accounts are configured and the admin interface is reachable. Check whether local or remote admin authentication is required and functional.
    Affected if Administrator authentication is configured and the admin panel is accessible, combined with a firmware version below 2.31F01.

The environment is affected if the Copeland E3 Supervisory Controller is running firmware version 2.30 or below (any version prior to 2.31F01) and the admin upgrade functionality is accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.31f01 or later
Fixed in 2.31f01
Interim mitigation

Upgrade E3 Site Supervisor Control firmware to version 2.31F01 or later which implements signed firmware packages, and verify the signing chain in the update mechanism.

Recommended fix High confidence

E3 Supervisory Controller Firmware version 2.31F01 or later

  1. Obtain the official firmware version 2.31F01 or later from the E3 Supervisory Controller vendor
  2. Download the firmware upgrade package from an official vendor source
  3. Verify the firmware package signature before installation if verification tools are provided by the vendor
  4. Access the E3 Site Supervisor Control administrative interface
  5. Navigate to the firmware upgrade or system update section
  6. Upload and apply the firmware version 2.31F01 or later
  7. Confirm the upgrade completes successfully and the device reboots
  8. Verify the installed firmware version is 2.31F01 or later
Caveat Review vendor release notes for any configuration or compatibility changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in E3 Supervisory Controller Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-52550 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-52550 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data