CVE Intelligence

TP-Link Systems Inc. Omada Controller vulnerabilities

🔔 Create alert RSS Version checker

Published CVEs affecting TP-Link Systems Inc. Omada Controller: 5 record(s), with affected versions and fixes.
cpe:2.3:a:tp-link:omada_controller

CVE-2025-9522 Medium · 5.3 CWE-918 Jan 26, 2026
Blind Server-Side Request Forgery (SSRF) in Omada Controller
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.
CVE-2025-9521 Medium · 6.5 CWE-522 Jan 26, 2026
Password Confirmation Bypass in Omada Controller
Password Confirmation Bypass vulnerability in Omada Controllers, allowing an attacker with a valid session token to bypass secondary verification, and change the user’s password without proper confirmation, leading to weakened account security.
CVE-2025-9520 Medium · 6.8 CWE-639 Jan 26, 2026
IDOR Leading to Owner Account Hijacking in Omada Controller
An IDOR vulnerability exists in Omada Controllers that allows an attacker with Administrator permissions to manipulate requests and potentially hijack the Owner account.
CVE-2025-9290 Medium · 5.9 CWE-760 Jan 22, 2026
Authentication Weakness on Omada Controllers, Gateways and Access Points
An authentication weakness was identified in Omada Controllers, Gateways and Access Points, controller-device adoption due to improper handling of random values. Exploitation requires advanced network positioning and allows an attacker to intercept adoption traffic and forge valid authentication through offline precomputation, potentially exposing sensitive information and compromising confidentiality.
CVE-2025-9289 Medium · 4.7 CWE-79 Jan 22, 2026
Cross-Site Scripting (XSS) on Omada Controllers
A Cross-Site Scripting (XSS) vulnerability was identified in a parameter in Omada Controllers due to improper input sanitization. Exploitation requires advanced conditions, such as network positioning or emulating a trusted entity, and user interaction by an authenticated administrator. If successful, an attacker could execute arbitrary JavaScript in the administrator’s browser, potentially exposing sensitive information and compromising confidentiality.