dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-27212

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
An Improper Input Validation in certain UniFi Access devices could allow a Command Injection by a malicious actor with access to UniFi Access management network. Affected Products: UniFi Access Reader Pro (Version 2.14.21 and earlier) UniFi Access G2 Reader Pro (Version 1.10.32 and earlier) UniFi Access G3 Reader Pro (Version 1.10.30 and earlier) UniFi Access Intercom (Version 1.7.28 and earlier) UniFi Access G3 Intercom (Version 1.7.29 and earlier) UniFi Access Intercom Viewer (Version 1.3.20 and earlier) Mitigation: Update UniFi Access Reader Pro Version 2.15.9 or later Update UniFi Access G2 Reader Pro Version 1.11.23 or later Update UniFi Access G3 Reader Pro Version 1.11.22 or later Update UniFi Access Intercom Version 1.8.22 or later Update UniFi Access G3 Intercom Version 1.8.22 or later Update UniFi Access Intercom Viewer Version 1.4.39 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 confidence

This is a command injection vulnerability caused by improper input validation in UniFi Access devices. An attacker with access to the UniFi Access management network can inject malicious commands through unsanitized input fields, potentially gaining full control of the affected device.

MitigationUpdate all affected UniFi Access devices to the specified minimum versions (Reader Pro 2.15.9+, G2 Reader Pro 1.11.23+, G3 Reader Pro 1.11.22+, Intercom 1.8.22+, G3 Intercom 1.8.22+, Intercom Viewer 1.4.39+). Since the attacker requires access to the management network, ensure proper network segmentation and access controls are in place as defense-in-depth.

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 checks

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

  1. Identify UniFi Access devices on the network
    Check your network inventory or scan for devices with hostnames containing 'UniFi Access', 'Reader', or 'Intercom', or look for devices with MAC OUI matching Ubiquiti. Access the UniFi Controller or UniFi OS console to view managed devices.
    Affected if Any UniFi Access device (Reader Pro, G2 Reader Pro, G3 Reader Pro, Intercom, G3 Intercom, or Intercom Viewer) is present on the network.
  2. Check Reader Pro firmware version
    In UniFi OS console or UniFi Controller, navigate to the device page for Reader Pro and locate the firmware version field under the device status or settings.
    Affected if Reader Pro firmware version is lower than 2.15.9.
  3. Check G2 Reader Pro firmware version
    In UniFi OS console or UniFi Controller, navigate to the device page for G2 Reader Pro and locate the firmware version field under the device status or settings.
    Affected if G2 Reader Pro firmware version is lower than 1.11.23.
  4. Check G3 Reader Pro firmware version
    In UniFi OS console or UniFi Controller, navigate to the device page for G3 Reader Pro and locate the firmware version field under the device status or settings.
    Affected if G3 Reader Pro firmware version is lower than 1.11.22.
  5. Check Intercom and G3 Intercom firmware versions
    In UniFi OS console or UniFi Controller, navigate to the device pages for Intercom and G3 Intercom and locate the firmware version fields under device status or settings.
    Affected if Intercom firmware version is lower than 1.8.22, or G3 Intercom firmware version is lower than 1.8.22.
  6. Check Intercom Viewer firmware version
    In UniFi OS console or UniFi Controller, navigate to the device page for Intercom Viewer and locate the firmware version field under the device status or settings.
    Affected if Intercom Viewer firmware version is lower than 1.4.39.

A user is affected if any UniFi Access device (Reader Pro, G2 Reader Pro, G3 Reader Pro, Intercom, G3 Intercom, or Intercom Viewer) with a firmware version below the respective fixed version (2.15.9, 1.11.23, 1.11.22, 1.8.22, 1.8.22, or 1.4.39) is present and reachable from the management network.

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

Update all affected UniFi Access devices to the specified minimum versions (Reader Pro 2.15.9+, G2 Reader Pro 1.11.23+, G3 Reader Pro 1.11.22+, Intercom 1.8.22+, G3 Intercom 1.8.22+, Intercom Viewer 1.4.39+). Since the attacker requires access to the management network, ensure proper network segmentation and access controls are in place as defense-in-depth.

Recommended fix High confidence

UniFi Access Reader Pro >=2.15.9; UniFi Access G2 Reader Pro >=1.11.23; UniFi Access G3 Reader Pro >=1.11.22; UniFi Access Intercom >=1.8.22; UniFi Access G3 Intercom >=1.8.22; UniFi Access Intercom Viewer >=1.4.39

  1. 1. Identify the specific UniFi Access device model(s) in your deployment
  2. 2. Check the current firmware version of each device through the UniFi Access management interface
  3. 3. For UniFi Access Reader Pro: Upgrade to version 2.15.9 or later
  4. 4. For UniFi Access G2 Reader Pro: Upgrade to version 1.11.23 or later
  5. 5. For UniFi Access G3 Reader Pro: Upgrade to version 1.11.22 or later
  6. 6. For UniFi Access Intercom: Upgrade to version 1.8.22 or later
  7. 7. For UniFi Access G3 Intercom: Upgrade to version 1.8.22 or later
  8. 8. For UniFi Access Intercom Viewer: Upgrade to version 1.4.39 or later

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27212 — 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-27212 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