Skip to main content

UniFi Access CVE-2025-52665

CRITICAL
Missing Authentication for Critical Function (CWE-306)
2025-10-31 support@hackerone.com
10.0
CVSS 3.1 · Vendor: hackerone
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain access to management network
  2. Delivery
    Discover exposed UniFi Access API
  3. Exploit
    Send unauthenticated API request
  4. Execution
    Manipulate door-access controls
  5. Impact
    Compromise physical access control

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK

1 technique across 1 tactic: Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires network-level access to the UniFi management network, where the UniFi Access management API is reachable; on vulnerable versions (3.3.22 through 3.4.31) that API is exposed without any authentication (CWE-306), so no credentials, tokens, or user interaction are needed once management-network reachability exists. The primary limiting factor is network segmentation: an attacker must already be on, or able to route to, the management plane - this is NOT internet-wide unauthenticated access despite the CVSS AV:N metric. The flaw was introduced in Version 3.3.22 and does not affect versions before it or 4.0.21 and later, so version and deployment of the management plane bound the exposure.

Impact

Multiple signals point to this being a genuinely high-priority flaw, but with an important real-world caveat. The input CVSS is 10.0 with vector AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H (CWE-306, Missing Authentication for a Critical Function), and the EPSS score of 41.09% at the 99th percentile is exceptionally high - placing it among the most exploitation-likely CVEs tracked. However, the signals partially conflict: the CVSS encodes AV:N (full network reachability), while the vendor description explicitly scopes exploitation to 'an actor with access to the management network.' This means raw network-wide unauthenticated exploitation is NOT accurate - exploitation requires a foothold on, or reachability to, the UniFi management network segment, which is a meaningful limiting factor the CVSS:N does not capture. There is NO CISA KEV listing and NO public POC referenced in the provided data, so despite the near-top EPSS percentile, there is no confirmation of active exploitation or weaponized exploit code. Net assessment: treat as a real, urgent patch priority for any environment running the affected UniFi Access versions, but recognize the attack is gated behind management-network access rather than being internet-wide. Verify management-plane exposure with the vendor advisory before assuming full AV:N applicability.

Exploit ScenarioDerived

An attacker who has gained a position on the UniFi management network (e.g., via a compromised internal host, VLAN misconfiguration, or weakly segmented management plane) directly queries the UniFi Access management API, which in vulnerable versions is exposed without authentication. Because no credentials are required (PR:N, AC:L), the attacker reads and manipulates door-access configuration, potentially unlocking doors or altering access rules. No public exploit identified at time of analysis, though the trivial nature of the missing-authentication flaw makes exploitation straightforward for anyone already on the management segment.

Emergency Immediate action required. Why: CRITICAL + EPSS > 30%, no patch available.
No patch listed yet 41.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 18, 2026

Unauthenticated access to the UniFi Access management API in application versions 3.3.22 through 3.4.31 allows anyone who can reach the management network to take full control of the door access platform - enumerating and modifying doors, users, credentials and controllers - because the API was exposed without any authentication check (CWE-306). Ubiquiti scores it CVSS 10.0 (AV:N), while our assessment rates it AV:A: the realistic gate is management-plane reachability, not internet-wide exposure, so segmented deployments are materially less exposed. EPSS is 41.09% (99th percentile), indicating high predicted exploitation interest, but at time of analysis there is no CISA KEV listing and no public exploit identified at time of analysis - the vendor reports the flaw was introduced in 3.3.22 and fixed in 4.0.21.

RemediationAI

Vendor-released patch: upgrade UniFi Access to Version 4.0.21 or later, per Security Advisory Bulletin 056 (https://community.ui.com/releases/Security-Advisory-Bulletin-056/ce97352d-91cd-40a7-a2f4-2c73b3b30191); given the CVSS 10.0 rating and 99th-percentile EPSS score, treat this as an emergency change on any instance still in the 3.3.22-3.4.31 range. Where upgrading cannot happen immediately, the effective control is reachability: firewall the management API so only dedicated admin VLANs or jump hosts can reach it, and remove any NAT/port-forward or VPN-to-management path that exposes it more broadly - the trade-off is that administrators lose convenient access from general user or remote networks and must work through the restricted path. Additional compensating measures with their costs: disable or restrict cloud/remote management connectivity to the console (reduces remote administration convenience), and enable and forward Access application and controller logs to a SIEM with alerting on anomalous API calls, new admin sessions, door-permission or credential changes (log retention and tuning effort required, and detection is retrospective rather than preventive). Auditing Access logs for unexpected API activity during the exposure window is warranted, and because the API was unauthenticated, absence of admin login records is not evidence of absence of access.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is a classic CWE-306 missing authentication for a critical function, sitting in the management API of UniFi Access, Ubiquiti's physical door access control application (CPE cpe:2.3:a:ui:unifi_access). Rather than a memory-safety or injection bug, the defect is architectural: a management endpoint that should require an authenticated administrative session accepted requests without credentials, tokens or user interaction. Because the CVSS scope is Changed (S:C), successful abuse is not contained to the web application - the API governs doors, badges/credentials, schedules and the Access controllers and hubs it manages, so compromise propagates into the physical security domain. The regression window is narrow and well bounded: introduced in 3.3.22, affecting 3.3.22 through 3.4.31, and corrected in 4.0.21, with versions prior to 3.3.22 unaffected. Reachability is the practical constraint - the API lives on the management plane, so an attacker must already be on, or able to route into, that network segment; the difference between Ubiquiti's AV:N and the assessed AV:A is precisely this segmentation dependency, and it is the dominant factor in real-world risk.

Know when Unifi Access gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (hackerone) PRIMARY 10.0 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
vuln.today AI 9.6 CRITICAL

Vendor restricts exploitation to the management network, so AV:A rather than AV:N; missing authentication gives PR:N and AC:L, and compromise of the door-access API changes scope to physical access systems (S:C).

3.1 AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
4.0 AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:H/SA:N

Primary rating from Vendor (hackerone).

CVSS VectorVendor: hackerone

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

A malicious actor with access to the management network could exploit a misconfiguration in UniFi’s door access application, UniFi Access, that exposed a management API without proper authentication. This vulnerability was introduced in Version 3.3.22 and was fixed in Version 4.0.21 and later.

Affected Products: UniFi Access Application (Version 3.3.22 through 3.4.31).

Mitigation: Update your UniFi Access Application to Version 4.0.21 or later.

Executive ViewAI

Why It Matters

Ubiquiti UniFi Access versions 3.3.22 through 3.4.31 expose a management API that, if reachable from the management network, can be used to take full control of doors, users, credentials, and controllers, creating material physical-security and safety risk. Leadership should treat this as a critical exposure limited primarily by management-plane segmentation; EPSS is elevated at 41.1%, but no public exploit has been identified at time of analysis.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis; vendor reports fix in 4.0.21, so verify availability before upgrading. Interim mitigations: strictly segment and firewall the UniFi Access management API so only trusted admin hosts can reach it; disable unnecessary management interfaces and remote access; monitor and alert on API enumeration, door/user/credential changes, and controller configuration changes; rotate credentials if suspicious activity is observed.

Threat Intelligence Overview

Threat Score
4.7/10
Composite threat intelligence
EPSS Score
41.1%
Top 1% exploitable
Prevalence
Medium
popular vendor door-access appliance, common in SMB/enterprise but not everywhere
Exploit
POC
Public exploit code exists
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC Yes
EPSS 41.1%
Patch available No
Active threat Yes
Deciding rule
CRITICAL + EPSS > 30%, no patch available
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
Poc
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
Very High

Priority Score

111
Low Medium High Critical
KEV: 0
EPSS: +41
CVSS: +50
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Affected Products (CPE)CVE.org

cpe:2.3:a:ui:unifi_access:*:*:*:*:*:*:*:*

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy