CVE-2025-27216
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 · uneditedMultiple Incorrect Permission Assignment for Critical Resource in UISP Application may allow a malicious actor with certain permissions to escalate privileges.
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 confidenceThis is a Broken Access Control vulnerability in Ubiquiti's UISP (ISP) application where multiple permission assignments for critical resources are incorrectly configured, allowing authenticated users with limited privileges to escalate to higher permission levels.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 installed UISP versionAccess the UISP administrative interface or check system documentation to locate the currently installed version number of the UISP applicationAffected if The installed version falls within any affected version range published by Ubiquiti for this CVE
-
Review user account rolesNavigate to the UISP user management section and list all user accounts along with their assigned roles and permission levelsAffected if Multiple users exist with different role assignments indicating role-based access control is in use
-
Examine permission assignments for critical resourcesIn the UISP admin panel, access the permissions or access control settings and inspect how permissions are assigned to roles for critical resources such as network devices, client data, or system configurationsAffected if Critical resources have permission assignments that allow access beyond the intended role scope
-
Test limited user access boundariesLog in with a user account that has restricted or non-administrative privileges and attempt to access functions, data, or settings typically reserved for higher-privilege rolesAffected if A limited user can view, modify, or delete resources or perform actions that should require elevated permissions
-
Audit role permission configurationCompare the defined permissions for each role in the UISP access control settings against the principle of least privilege, looking for role definitions that grant excessive access to critical resourcesAffected if Any role contains permission configurations that grant access to resources beyond what that role should logically require
The environment is affected if limited-privilege users can access or modify critical resources or functions that should be restricted to higher-privilege roles.
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.
From vendor dataReview and correct all permission assignments for critical resources in UISP, ensuring users can only access resources appropriate to their role; apply any vendor security patches immediately.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27216 — 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-27216 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