dbcve.org
E3 Supervisory Controller FirmwareOperating system · Copeland

CVE-2025-52543

HIGH · 7.5 CVSS v3.1 Published 2025-09-02
Fix available
A fix is available. Upgrade to 2.31f01 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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) application services (MGW and RCI) uses client side hashing for authentication. An attacker can authenticate by obtaining only the password hash.

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 uses client-side hashing for authentication in its MGW and RCI services. An attacker who obtains the password hash can use it directly to authenticate without needing the plaintext password, effectively bypassing the authentication mechanism.

MitigationUpgrade E3 Site Supervisor Control firmware to version 2.31F01 or later which implements proper server-side authentication. Until patched, treat password hashes as sensitive credentials and monitor for unauthorized access attempts.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Determine the installed firmware version
    Access the E3 Site Supervisor Control web interface or check the controller system information page to identify the current firmware version. Alternatively, use the device's administrative console or check the system status for the firmware build number.
    Affected if The installed firmware version is earlier than 2.31f01 (for example, 2.30, 2.29, or any version with a build number below 2.31F01).
  2. Verify if MGW service is accessible
    Check if the MGW (Modbus Gateway) service port is open and responding on the E3 controller. This can be done by attempting a network connection to the typical MGW port or reviewing the device's service configuration.
    Affected if The MGW service is enabled and accessible on the network, and the firmware version is earlier than 2.31f01.
  3. Verify if RCI service is accessible
    Check if the RCI (Remote Controller Interface) service port is open and responding on the E3 controller. This can be done by attempting a network connection to the typical RCI port or reviewing the device's service configuration.
    Affected if The RCI service is enabled and accessible on the network, and the firmware version is earlier than 2.31f01.
  4. Review authentication mechanism in use
    Examine the authentication configuration for MGW and RCI services through the E3 administrative interface. Look for whether the system uses client-side hashing (sending hashed password) rather than server-side challenge-response authentication.
    Affected if The MGW or RCI services are configured to use client-side hashing for authentication, and the firmware version is earlier than 2.31f01.

The environment is affected if the E3 Site Supervisor Control firmware version is earlier than 2.31f01 and either the MGW or RCI service is accessible with client-side hashing authentication enabled.

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 proper server-side authentication. Until patched, treat password hashes as sensitive credentials and monitor for unauthorized access attempts.

Recommended fix High confidence

2.31F01

  1. 1. Identify the current firmware version of the E3 Supervisory Controller by accessing the device management interface or checking the device status.
  2. 2. Download firmware version 2.31F01 or later from the official Vertiv or E3 controller vendor source.
  3. 3. Follow the vendor's documented firmware update procedure to apply version 2.31F01 to the E3 Supervisory Controller.
  4. 4. After updating, verify the firmware version displays as 2.31F01 or higher in the device management interface.
  5. 5. Confirm that MGW and RCI services now require proper authentication (not just password hash) for access.

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-52543 — 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-52543 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