Owner account takeover via unchecked password reset
Published Jan 26, 2026 · Updated Jan 26, 2026
Authorization bypass in TP-Link Systems Inc. Omada Controller before 6.0 allows remote authenticated users to hijack the Owner account. The account-management backend accepts an Owner identifier in a direct password-change request, changes the password despite returning HTTP 403, and fails to enforce the interface's role restriction. Administrator access is required; successful exploitation grants full control of the controller and its connected services.
Summary
What happened
Authorization bypass in TP-Link Systems Inc. Omada Controller before 6.0 allows remote authenticated users to hijack the Owner account. The account-management backend accepts an Owner identifier in a direct password-change request, changes the password despite returning HTTP 403, and fails to enforce the interface's role restriction. Administrator access is required; successful exploitation grants full control of the controller and its connected services.
The record
- CVE
- CVE-2025-9520
- Published
- Jan 26, 2026
- Updated
- Jan 26, 2026
- Vendor
- TP-Link Systems Inc.
- Product
- Omada Controller
- Classifications
- CWE-639, T1098
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jan 26, 2026CVE publishedPublication date reported by the CVE source.
- Jan 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <6.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo