Skip to content
Fencer Intel
critical 10.0

CVE-2025-52665 in the critical feed json

A malicious actor with access to the management network could exploit a misconfiguration in UniFi’s door access application, UniFi Access,…

published last yr. modified 22d ago also EUVD-2025-37233

cvss
10.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
41.1%
EPSS 41.1% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known, plus a Nuclei check

Summary

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.

Patch / fix

  • ui unifi_access 4.0.21

Is CVE-2025-52665 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
last yr.

Exploit prediction

41.09% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

CVSS scores

assigned by version score vector
CISA ADP 3.1 10.0 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CNA 3.1 10.0 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Affected products

  • Ubiquiti Inc UniFi Access Application

Classification

Weakness
  • CWE-306 Missing Authentication for Critical Functionality

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.