CVE-2025-27217
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 · uneditedA Server-Side Request Forgery (SSRF) in the UISP Application may allow a malicious actor with certain permissions to make requests outside of UISP Application scope.
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 confidenceUISP Application contains a Server-Side Request Forgery (SSRF) vulnerability that allows authenticated users with specific permissions to make arbitrary HTTP requests to external systems, potentially exposing internal network infrastructure, cloud metadata services, or enabling further pivoting into internal systems.
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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm UISP installationIdentify if UISP (formerly UniFi Network) is running in your environment by checking for the application process, web service on typical ports (443, 8080), or installation directories.Affected if UISP is not installed - vulnerability does not apply.
-
Determine installed UISP versionAccess the UISP web interface and navigate to the system settings or about page to find the exact version number. Alternatively, check the application binaries or package manager if you have server access.Affected if Unable to determine version - assume potentially affected and investigate further.
-
Verify user authentication is enabledCheck if the UISP application has authentication configured and active. Confirm that user accounts exist and the login mechanism is functional.Affected if Authentication is disabled - the SSRF may still be accessible but the vulnerability description indicates authenticated users, so verify your authentication configuration.
-
Identify privileged user accountsReview UISP user management settings to list accounts and their assigned permission levels. Look for users with permissions that include API access, network diagnostics, or external request capabilities.Affected if Users with elevated permissions (such as admin or network operator roles) exist in the system - these accounts could trigger the vulnerable functionality.
-
Check for outbound HTTP request functionalityExamine UISP configuration files and web interface for features that allow users to specify URLs or make HTTP requests (such as ping, traceroute to URL, webhooks, or external service integrations).Affected if The feature allowing arbitrary HTTP requests from the application is present and accessible to authenticated users.
If UISP is installed and authenticated users with the relevant permissions can access functionality that makes HTTP requests, your environment is likely affected by this SSRF vulnerability.
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 dataImplement strict URL/hostname allowlisting and validate all user-supplied URLs before making outbound requests; restrict outbound network access from the application to prevent requests to internal IP ranges and metadata endpoints.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27217 — 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-27217 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