Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-9522: CWE-918 Server-Side Request Forgery (SSRF) in TP-Link Systems Inc. Omada Controller

0
Medium
VulnerabilityCVE-2025-9522cvecve-2025-9522cwe-918
Published: Mon Jan 26 2026 (01/26/2026, 19:35:59 UTC)
Source: CVE Database V5
Vendor/Project: TP-Link Systems Inc.
Product: Omada Controller

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.

AI-Powered Analysis

AILast updated: 01/26/2026, 20:06:17 UTC

Technical Analysis

CVE-2025-9522 is a Server-Side Request Forgery (SSRF) vulnerability classified under CWE-918, affecting TP-Link Systems Inc.'s Omada Controller product. The vulnerability arises from the webhook functionality, which improperly handles crafted requests, allowing an attacker to induce the server to send requests to internal services that are otherwise inaccessible externally. This is a blind SSRF, meaning the attacker does not directly see the response but can infer information based on side effects or timing. The flaw requires the attacker to have high privileges (authenticated access) to the Omada Controller, and no user interaction is needed beyond that. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:H means high privileges required), no user interaction (UI:N), and low impact on confidentiality (VC:L), with no impact on integrity or availability. The vulnerability could allow enumeration of internal network services, potentially exposing sensitive information such as internal IP addresses, service versions, or other metadata that could facilitate further exploitation. No patches or known exploits are currently available, but the vulnerability is publicly disclosed and should be addressed proactively. The Omada Controller is widely used for managing network devices and infrastructure, making this vulnerability significant for organizations relying on it for network management.

Potential Impact

For European organizations, the SSRF vulnerability in Omada Controller could lead to unauthorized internal network reconnaissance, exposing sensitive infrastructure details. This could facilitate lateral movement, targeted attacks, or exploitation of other internal vulnerabilities. Organizations managing critical infrastructure, government networks, or large enterprise environments using Omada Controller are at particular risk. The ability to enumerate internal services can undermine network segmentation and defense-in-depth strategies, potentially leading to data breaches or service disruptions. Although exploitation requires authenticated access, insider threats or compromised credentials could be leveraged to exploit this vulnerability. The medium severity rating reflects moderate risk, but the impact could escalate if combined with other vulnerabilities or social engineering attacks. Given the widespread use of TP-Link Omada products in European SMBs and enterprises, the potential for impact is significant, especially in sectors with stringent data protection requirements such as finance, healthcare, and public administration.

Mitigation Recommendations

To mitigate CVE-2025-9522, organizations should implement the following specific measures: 1) Restrict webhook functionality to only allow requests to trusted, whitelisted internal endpoints, preventing arbitrary internal requests. 2) Enforce strict input validation and sanitization on webhook parameters to block crafted request payloads. 3) Apply network segmentation and firewall rules to limit the Omada Controller's ability to reach sensitive internal services unnecessarily. 4) Monitor and log all webhook-triggered requests and analyze logs for unusual or unauthorized internal access attempts. 5) Limit administrative access to the Omada Controller to trusted personnel and enforce strong authentication mechanisms, including multi-factor authentication. 6) Stay updated with TP-Link security advisories and apply patches promptly once available. 7) Conduct regular security assessments and penetration tests focusing on internal request handling and webhook features. These targeted actions go beyond generic advice by focusing on the specific attack vector and operational context of the Omada Controller.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
TPLink
Date Reserved
2025-08-27T02:22:08.375Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6977c5a14623b1157cb6ffa0

Added to database: 1/26/2026, 7:50:57 PM

Last enriched: 1/26/2026, 8:06:17 PM

Last updated: 1/26/2026, 9:50:07 PM

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats