# CVE-2025-27217: Server-side request forgery in UISP Application

> A malicious actor with permissions can exploit SSRF in UISP Application to make requests outside the intended scope.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2025
- **Updated:** 21 Aug 2025
- **Also known as:** GHSA-2789-ggx9-w3cc

## What is CVE-2025-27217?

CVE-2025-27217 is a critical server-side request forgery vulnerability in Ubiquiti Inc UISP Application, published on 21 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A 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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2025-27217?


## How do I fix CVE-2025-27217?

No fix has been published for CVE-2025-27217 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-27217 being exploited?

There is no known exploitation of CVE-2025-27217 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-27217 and fix it if it is affected.

What it is: CVE-2025-27217 is a critical server-side request forgery vulnerability in Ubiquiti Inc UISP Application, published on 21 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-27217 in the wild and no public exploit code.

Affected product: Ubiquiti Inc UISP Application. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-27217/ (Markdown: https://insights.sbomify.com/CVE-2025-27217/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-27217
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-27217
- OSV: https://osv.dev/vulnerability/CVE-2025-27217

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-27217/
Summaries are generated and may contain mistakes; the official description above is the record.