CVE-2025-52546
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 · uneditedE3 Site Supervisor Control (firmware version < 2.31F01) has a floor plan feature that allows for an unauthenticated attacker to upload floor plan files. By uploading a specially crafted floor plan file, an attacker can inject a stored XSS to the floorplan web page.
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 confidenceE3 Site Supervisor Control firmware versions before 2.31F01 contain a stored XSS vulnerability in the floor plan upload feature. An unauthenticated attacker can upload specially crafted floor plan files containing malicious JavaScript that executes when users view the floorplan web page.
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< 2.31f01CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify E3 Site Supervisor firmware versionAccess the E3 web interface and navigate to System > About or Settings > Firmware Information. Alternatively, check the login page or admin dashboard for the firmware version display.Affected if The displayed firmware version is below 2.31f01 (for example, 2.30, 2.29, etc.)
-
Verify floor plan module availabilityLog into the E3 Site Supervisor web interface and look for a Floor Plans, Building Layout, or Site Map feature in the navigation menu.Affected if The floor plan feature exists and is accessible in the web interface
-
Check for existing uploaded floor plansWithin the floor plan module, examine if any floor plan files have been uploaded to the system.Affected if Any floor plan files are present in the system (these could contain malicious payloads if uploaded by an attacker)
-
Inspect floor plan file metadataIf floor plan files are present, download or inspect them to check the file names, upload dates, and any embedded content that may contain suspicious script tags or JavaScript.Affected if Floor plan files contain script tags, event handlers, or JavaScript code in file names or embedded content
The environment is affected if the E3 Site Supervisor firmware version is below 2.31f01 AND the floor plan upload feature is accessible and contains uploaded files that could contain malicious scripts.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.31f01
Upgrade E3 Site Supervisor Control firmware to version 2.31F01 or later to remediate the vulnerability.
2.31F01 or later
- Identify all E3 Supervisory Controller devices in the environment running firmware versions prior to 2.31F01
- Obtain the firmware version 2.31F01 or later from the vendor's official distribution channel
- Review vendor upgrade documentation for any specific prerequisites or procedures
- Schedule a maintenance window for firmware upgrade following vendor-recommended procedures
- Upload and apply the firmware upgrade to each affected E3 Supervisory Controller
- Verify the upgrade was successful by confirming the new firmware version is 2.31F01 or later
- Test the floor plan upload functionality to confirm normal operation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52546 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-52546 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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