CVE-2025-9292
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 · uneditedA permissive web security configuration may allow cross-origin restrictions enforced by modern browsers to be bypassed under specific circumstances. Exploitation requires the presence of an existing client-side injection vulnerability and user access to the affected web interface. Successful exploitation could allow unauthorized disclosure of sensitive information. Fixed in updated Omada Cloud Controller service versions deployed automatically by TP‑Link. No user action is required.
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 confidenceThis is a cross-origin (CORS) bypass vulnerability in TP-Link Omada Cloud Controller where permissive web security configuration allows modern browser cross-origin restrictions to be circumvented. Successful exploitation requires chaining with an existing client-side injection vulnerability and user interaction with the web interface, potentially enabling unauthorized disclosure of sensitive information.
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< 2.13.6< 3.9.163< 1.7.1< 3.4.350< 1.1.21< 4.25.25< 1.1.28< 3.14.111CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify your TP-Link product and obtain the installed versionLog into the web interface or use the CLI command specific to your device (for Omada: Controller dashboard version info; for Tapo/Kasa: App or device settings; for Deco: Main unit settings). Locate the firmware or software version number displayed in the system information or about section.Affected if The installed version falls below any of these thresholds: Aginet < 2.13.6, Deco < 3.9.163, Festa < 1.7.1, Kasa < 3.4.350, Kidshield < 1.1.21, Omada < 4.25.25, Omada Guard < 1.1.28, Tapo < 3.14.111.
-
Verify if remote cloud management or cloud controller is enabledCheck the device or controller settings for cloud connectivity features. In Omada: go to Settings > Controller > Cloud Access. For Deco/Tapo/Kasa: check if the device is registered to a cloud account and remote management is active.Affected if The cloud controller or remote management feature is enabled and the device is accessible over the internet.
-
Inspect the web interface for existing client-side injection vulnerabilitiesReview any custom scripts, dynamic content rendering, or user-supplied input fields in the web interface. Look for reflected or stored XSS indicators in URL parameters or form submissions. Use a browser developer tool to examine network responses for unexpected script execution.Affected if Any exploitable client-side injection (XSS) vulnerability exists in the web interface that could be chained with the CORS bypass.
-
Review CORS policy configuration in HTTP responsesUsing a browser or HTTP tool, access the login or API endpoints of the cloud controller and inspect the Access-Control-Allow-Origin header in responses. Check if the policy allows arbitrary origins (wildcard (*) or multiple domains) without proper validation.Affected if The Access-Control-Allow-Origin header permits unrestricted or overly permissive cross-origin requests.
Your environment is affected if the installed TP-Link software version is below the fixed versions listed AND you have cloud management enabled AND a client-side injection vulnerability exists that could be chained with the permissive CORS configuration.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.1.211.1.281.7.1
The fix is automatically deployed via updated Omada Cloud Controller service versions - verify with TP-Link that your instance has received the update. Additionally, identify and remediate any existing client-side injection vulnerabilities in the web interface, as these are required for exploitation.
Aginet ≥2.13.6, Deco ≥3.9.163, Festa ≥1.7.1, Kasa ≥3.4.350, Kidshield ≥1.1.21, Omada ≥4.25.25, Omada Guard ≥1.1.28, Tapo ≥3.14.111 (Omada Cloud Controller receives automatic updates)
- For Omada Cloud Controller: No user action required - updates are deployed automatically by TP-Link
- For other affected products (Aginet, Deco, Festa, Kasa, Kidshield, Tapo): Check your current version in the device/application settings
- Upgrade to version 2.13.6 or later for Aginet
- Upgrade to version 3.9.163 or later for Deco
- Upgrade to version 1.7.1 or later for Festa
- Upgrade to version 3.4.350 or later for Kasa
- Upgrade to version 1.1.21 or later for Kidshield
- Upgrade to version 4.25.25 or later for Omada (standalone)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9292 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-9292 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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