CVE-2025-9289 — 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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (TP-Link Systems Inc. Oc200 Firmware, TP-Link Systems Inc. Oc220 Firmware, TP-Link Systems Inc. Oc300 Firmware…).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Exploitation requires user interaction: tighten email/web filtering and warn affected users.
- Search available logs for exploit probes matching the vulnerability class (cross-site scripting), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| TP-Link Systems Inc. | Oc200 Firmware | < 1.37.9< 2.22.9 | Vulnerable | NIST National Vulnerability Database |
| TP-Link Systems Inc. | Oc220 Firmware | < 1.2.9 | Vulnerable | NIST National Vulnerability Database |
| TP-Link Systems Inc. | Oc300 Firmware | < 1.31.9 | Vulnerable | NIST National Vulnerability Database |
| TP-Link Systems Inc. | Oc400 Firmware | < 1.9.9 | Vulnerable | NIST National Vulnerability Database |
| TP-Link Systems Inc. | Omada Cloud Controller | < 6.0.0.100 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| TP-Link Systems Inc. | Omada Controller | < 6.0.0.24< 6.0.0.100< 6.0.0.34 | Vulnerable | NIST National Vulnerability Database |
| TP-Link Systems Inc. | Omada OC200, OC220, OC300, OC400 | < 6.0.0.34 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| TP-Link Systems Inc. | Omada Software Controller | < 6.0.0.24 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 5.7 | CVSS 4.0 | Medium | — | — | f23511db-6c3e-4e32-a477-6aa17d310630 via NIST National Vulnerability Database |
| 5.7 | CVSS 4.0 | Medium | — | — | TPLink via CVE Program (cve.org) e CISA ADP |
| 4.7 | CVSS 3.1 | Medium | 1.6 | 2.7 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.20%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Monitor CSP violation reports and script payloads in reflected parameters.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · tp-link systems inc./omada software controller, tp-link systems inc./omada oc200, oc220, oc300, oc400, tp-link systems i
- SSVC assessment updated
- Record published
- CVSS changed · 4.7
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
2 on the record
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-107795 Improper Authorization in TP-Link Omada Controller TLS Certificate and Private Key Management API 21h
- Medium CVE-2025-9522 Blind Server-Side Request Forgery (SSRF) in Omada Controller Jan 26, 2026
- Medium CVE-2025-9520 IDOR Leading to Owner Account Hijacking in Omada Controller Jan 26, 2026
- Medium CVE-2025-9521 Password Confirmation Bypass in Omada Controller Jan 26, 2026
- Medium CVE-2025-9290 Authentication Weakness on Omada Controllers, Gateways and Access Points Jan 22, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-9289 is "Cross-Site Scripting (XSS) on Omada Controllers", rated Medium. It affects Oc200 Firmware (TP-Link Systems Inc.); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.7 describes technical severity. EPSS 0.20% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.