CVE-2025-52551
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 · uneditedE2 Facility Management Systems use a proprietary protocol that allows for unauthenticated file operations on any file in the file system.
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 confidenceE2 Facility Management Systems contain a vulnerability in their proprietary protocol that allows unauthenticated attackers to perform file operations on any file in the system's filesystem. This critical flaw bypasses all authentication controls, enabling arbitrary file read/write/delete access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 E2 Facility Management Systems in your environmentInventory all systems running E2 Facility Management software. Check asset inventories, network scans, or consult system administrators for systems labeled as facility management, building management, or E2 systems.Affected if E2 Facility Management Systems are present in the environment
-
Determine network exposure of the proprietary protocolReview firewall rules, network segments, and access control lists to identify whether the E2 proprietary protocol (typically on ports used by E2 for device communication) is accessible from untrusted networks, the internet, or non-segmented network zones.Affected if The proprietary protocol is exposed to untrusted networks or accessible without network-level access controls
-
Verify if file operation functions are enabled and accessibleConsult E2 system documentation or configuration settings to determine whether file operation capabilities within the proprietary protocol are enabled. Check if there are any access control lists or restrictions on file operation functions.Affected if File operation functions in the proprietary protocol are enabled and accessible to network users
-
Test for unauthenticated file accessIf you have authorization, use the proprietary protocol client or a test tool to attempt unauthenticated file operations (read, write, delete) on files outside the expected operational directories. Observe whether the system permits these operations without credentials.Affected if The system allows file operations without authentication through the proprietary protocol
You are affected if you have E2 Facility Management Systems with the proprietary protocol exposed to the network and file operation functions enabled, allowing unauthenticated file access.
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.
From vendor dataRestrict network access to E2 Facility Management Systems via firewall or VLAN segmentation, and implement strong authentication and authorization controls on the proprietary protocol's file operation functions.
- Consultation12.0 h
- Implementation32.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $19,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52551 — 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-52551 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