dbcve.org
Omada ControllerOperating system · Tp Link

CVE-2025-9522

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-26
Fix available
A fix is available. Upgrade to 6.0 or later.
See remediation →
62/100
Remediation priority · Elevated
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
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.

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 confidence

A blind Server-Side Request Forgery (SSRF) vulnerability exists in the webhook functionality of TP-Link Omana Controllers. Attackers can craft malicious webhook requests that cause the server to make connections to internal services, potentially enabling reconnaissance and enumeration of internal infrastructure.

MitigationImplement strict URL validation and allowlisting for webhook endpoints to restrict outbound requests to trusted destinations. Additionally, enforce network segmentation to limit the impact of SSRF attempts on internal services.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Omada ControllerOperating system
Affected:< 6.0

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checks

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

  1. Identify installed Omada Controller version
    Access the controller's admin UI or check system information page. If using Linux, check /opt/tplink/OmadaController/version.properties or similar version file. CLI: 'omada-ctl status' or check the web interface under 'Settings > Controller > About'.
    Affected if The installed version is any version prior to 6.0 (e.g., 5.x, 5.14.x, 5.0.x). Versions 6.0 and later are not affected.
  2. Verify if webhook functionality is accessible
    Navigate to the Omada Controller web UI, go to 'Settings' > 'Notification' or 'Webhook' settings. Check if any webhook endpoints are configured under the webhook or notification settings section.
    Affected if Webhooks or notification webhooks are enabled and at least one webhook URL is configured in the controller.
  3. Inspect configured webhook URLs
    In the webhook configuration panel, review all configured webhook endpoint URLs. Look for any HTTP/HTTPS URLs pointing to internal network addresses (127.0.0.1, 192.168.x.x, 10.x.x.x, internal hostnames) or sensitive internal services.
    Affected if Any webhook is configured to point to internal/direct IP addresses or internal network ranges without proper URL validation.
  4. Check network exposure of controller
    Determine if the Omada Controller management interface is accessible from untrusted networks. Review firewall rules, port forwards, or cloud deployment settings that expose the controller's web UI.
    Affected if The controller's web interface is exposed to the internet or untrusted networks, allowing external attackers to reach the webhook functionality.

You are affected if your TP-Link Omada Controller version is below 6.0 AND webhooks are enabled with a configured endpoint, as this combination allows attackers to trigger blind SSRF requests from your controller.

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
Upgrade available Upgrade to 6.0 or later
Fixed in 6.0
Interim mitigation

Implement strict URL validation and allowlisting for webhook endpoints to restrict outbound requests to trusted destinations. Additionally, enforce network segmentation to limit the impact of SSRF attempts on internal services.

Recommended fix Moderate confidence

Omada Controller 6.0

  1. Upgrade Omada Controller to version 6.0 or later to remediate the SSRF vulnerability
  2. After upgrade, verify the webhook functionality is working as expected
  3. Review access controls and network segmentation to limit potential impact of any remaining webhook-related vulnerabilities
  4. If upgrading is not immediately possible, restrict access to the Omada Controller management interface to trusted networks only
Caveat Review Omada Controller 6.0 release notes for any changes to webhook functionality or other features that may affect your deployment

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

Fix this in Omada Controller Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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