# CVE-2025-9522: Blind Server-Side Request Forgery (SSRF) in Omada Controller

> Attackers can exploit blind SSRF in Omada Controller webhooks to enumerate internal services and access sensitive information.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jan 2026
- **Updated:** 3 Feb 2026
- **Also known as:** GHSA-grjh-4c57-c7g8

## What is CVE-2025-9522?

CVE-2025-9522 is a medium-severity server-side request forgery vulnerability in TP-Link Systems Inc. Omada Controller, published on 26 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Blind Server-Side Request Forgery (SSRF) in Omada Controllers through webhook functionality, enabling crafted requests to internal services, which may lead to enumeration of information.

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

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

It affects 1 product.


Products: Tp-Link Omada Controller.

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

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

## Is CVE-2025-9522 being exploited?

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

## Other vulnerabilities in TP-Link Systems Inc. Omada Controller

- [CVE-2025-9520](https://insights.sbomify.com/CVE-2025-9520/): IDOR Leading to Owner Account Hijacking in Omada Controller (high 8.3)
- [CVE-2020-12475](https://insights.sbomify.com/CVE-2020-12475/): Path traversal in n/a (medium 5.5)
- [CVE-2025-9521](https://insights.sbomify.com/CVE-2025-9521/): Password Confirmation Bypass in Omada Controller (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9522 is a medium-severity server-side request forgery vulnerability in TP-Link Systems Inc. Omada Controller, published on 26 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-9522 in the wild and no public exploit code.

Affected product: TP-Link Systems Inc. Omada Controller. 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-9522/ (Markdown: https://insights.sbomify.com/CVE-2025-9522/index.md)
```

## Sources

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

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