dbcve.org
E3 Supervisory Controller FirmwareOperating system · Copeland

CVE-2025-52547

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) MGW contains an API call that lacks input validation. An attacker can use this command to continuously crash the application services.

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 · moderate confidence

The E3 Site Supervisor Control MGW firmware versions prior to 2.31F01 contain an API endpoint that lacks proper input validation. Attackers can send malformed requests to this API to trigger continuous crashes of the application services, causing denial of service.

MitigationUpgrade the E3 Site Supervisor Control MGW firmware to version 2.31F01 or later to obtain the input validation fix. If immediate patching is not possible, restrict network access to the MGW management interface to trusted sources only.

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 device model
    Locate the E3 Site Supervisor Control MGW device on your network and confirm the model number matches the affected product line.
    Affected if The device is not an E3 Site Supervisor Control MGW unit.
  2. Determine the installed firmware version
    Access the MGW web interface or use the device's diagnostic tools to retrieve the current firmware version. This is typically found under System Information, About, or Firmware Update sections of the management interface.
    Affected if The firmware version is lower than 2.31F01 (for example, 2.30, 2.29, or earlier).
  3. Verify API endpoint accessibility
    Check if the MGW management interface API endpoint is reachable from network segments that contain untrusted or external systems. Attempt to access the API endpoint using the device's IP address and documented API paths.
    Affected if The API endpoint is exposed to untrusted network segments without network segmentation or firewall controls.
  4. Check for service stability issues
    Review system logs, event logs, or monitoring alerts for the MGW device. Look for repeated service crashes, unexpected restarts, or denial-of-service indicators around the API endpoint.
    Affected if The device shows repeated unexplained service crashes or requires frequent reboots.

You are affected if your E3 Site Supervisor Control MGW is running firmware version 2.31F01 or lower AND the management API is accessible from your network.

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 the E3 Site Supervisor Control MGW firmware to version 2.31F01 or later to obtain the input validation fix. If immediate patching is not possible, restrict network access to the MGW management interface to trusted sources only.

Recommended fix Moderate confidence

2.31F01

  1. 1. Identify the current firmware version of the E3 Supervisory Controller by accessing the device management interface or using the vendor's diagnostic tool.
  2. 2. Download the fixed firmware version 2.31F01 (or later) from the official vendor support portal or through your authorized distributor.
  3. 3. Review the vendor's firmware upgrade documentation for any specific prerequisites or procedures.
  4. 4. Apply the firmware upgrade to the E3 Supervisory Controller following the vendor's recommended process (typically via web UI, USB, or network-based deployment).
  5. 5. After upgrading, verify that the device is running version 2.31F01 or later.
  6. 6. Test the MGW API functionality to confirm the application services are running stably and the input validation fix is functioning.

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
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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