dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2025-24292

MEDIUM · 6.8 CVSS v3.0 Published 2025-06-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
A misconfigured query in UniFi Network (v9.1.120 and earlier) could allow users to authenticate to Enterprise WiFi or VPN Server (l2tp and OpenVPN) using a device’s MAC address from 802.1X or MAC Authentication, if both services are enabled and share the same RADIUS profile.

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 confidence

UniFi Network v9.1.120 and earlier contains a misconfiguration where authentication to Enterprise WiFi (via 802.1X) or VPN Server (L2TP/OpenVPN) can be bypassed by using a device's MAC address when both services are enabled and share the same RADIUS profile. This allows an attacker who has captured a valid MAC address from 802.1X or MAC Authentication to authenticate to the VPN service without proper credentials.

MitigationSeparate the RADIUS profiles used by Enterprise WiFi and VPN Server so they do not share the same configuration. If possible, update to a patched version when available.

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
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check UniFi Network version
    Locate the installed UniFi Network Controller version in the system settings or controller dashboard. Compare this version number to 9.1.120 (any version at or below 9.1.120 is affected).
    Affected if The installed UniFi Network version is 9.1.120 or earlier.
  2. Verify Enterprise WiFi (802.1X) is enabled
    Access the UniFi Network settings and examine the wireless network configurations. Look for any WiFi network configured with WPA-Enterprise or 802.1X authentication method.
    Affected if Enterprise WiFi with 802.1X authentication is enabled and configured.
  3. Verify VPN Server is enabled
    Access the UniFi Network VPN settings. Check whether L2TP VPN or OpenVPN server is currently active and accepting connections.
    Affected if L2TP or OpenVPN server is enabled in the VPN configuration.
  4. Identify RADIUS profile configuration
    Examine the RADIUS server settings used by both the Enterprise WiFi and VPN Server. Determine whether they reference or share the same RADIUS profile configuration (same RADIUS server IP, shared secret, and profile settings).
    Affected if Enterprise WiFi and VPN Server are both using the identical RADIUS profile configuration.

A system is affected only if it runs UniFi Network v9.1.120 or earlier AND has both Enterprise WiFi (802.1X) and VPN Server (L2TP/OpenVPN) enabled AND both services share the same RADIUS profile.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Separate the RADIUS profiles used by Enterprise WiFi and VPN Server so they do not share the same configuration. If possible, update to a patched version when available.

Recommended fix Moderate confidence

UniFi Network v9.1.121 or later (check Ubiquiti Downloads for latest stable release)

  1. 1. Back up your UniFi Network configuration before performing any upgrade.
  2. 2. Access the UniFi Network Controller (on-premises or UniFi OS).
  3. 3. Navigate to Settings > System > Advanced (or check for available updates in the controller).
  4. 4. If using UniFi OS Console, go to Settings > UniFi OS > Check for Updates.
  5. 5. Upgrade UniFi Network to version 9.1.121 or later.
  6. 6. After upgrade, verify that Enterprise WiFi and VPN Server (L2TP and OpenVPN) are not sharing the same RADIUS profile if both are enabled.
  7. 7. Test authentication to confirm the vulnerability is remediated.
Caveat Review Ubiquiti release notes for 9.1.121 for any configuration or feature changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24292 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-24292 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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