CVE-2025-27214
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 · uneditedA Missing Authentication for Critical Function vulnerability in the UniFi Connect EV Station Pro may allow a malicious actor with physical or adjacent access to perform an unauthorized factory reset. Affected Products: UniFi Connect EV Station Pro (Version 1.5.18 and earlier) Mitigation: Update UniFi Connect EV Station Pro to Version 1.5.27 or later
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 confidenceUniFi Connect EV Station Pro versions 1.5.18 and earlier lack authentication checks on the factory reset function. An attacker with physical access or adjacent network proximity can trigger an unauthorized factory reset, potentially gaining full device control or causing service disruption.
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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify device modelAccess the UniFi Connect management interface or check the physical device label to confirm the model is UniFi Connect EV Station ProAffected if Device is not a UniFi Connect EV Station Pro, then it is not affected by this specific CVE
-
Check installed firmware versionLog into the UniFi Connect controller or device web interface and navigate to the device settings or system information page to view the current firmware versionAffected if Firmware version cannot be determined or accessed, preventing version comparison
-
Compare version against affected rangeCompare the installed firmware version number to the affected range: 1.5.18 and earlier. Version 1.5.18 or any version lower than 1.5.18 is affectedAffected if Installed firmware version is 1.5.18 or earlier (e.g., 1.5.17, 1.5.16, etc.)
-
Assess network exposureCheck if the device management interface is accessible from untrusted networks or verify physical security controls around the deviceAffected if Device is exposed to untrusted network segments or physically accessible to unauthorized persons, making the unauthenticated factory reset exploitable
The device is affected if it is a UniFi Connect EV Station Pro running firmware version 1.5.18 or earlier, and the factory reset function can be accessed without authentication due to lack of authentication checks.
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 · scopedUpdate UniFi Connect EV Station Pro firmware to version 1.5.27 or later to remediate the missing authentication vulnerability.
UniFi Connect EV Station Pro version 1.5.27 or later
- Access the UniFi Connect controller or management interface
- Navigate to the UniFi Connect EV Station Pro device settings
- Check the current firmware version (confirm it is 1.5.18 or earlier)
- Initiate firmware update to version 1.5.27 or later
- Verify the update was successful and the device is running the patched version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27214 — 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-27214 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