dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-14553

HIGH · 7.0 CVSS v4.0 Published 2025-12-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/100
Remediation priority · High
No privileges Zero-click

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 · unedited
Exposure of password hashes through an unauthenticated API response in TP-Link Tapo app on iOS and Android for Tapo cameras, allowing attackers to brute force the password in the local network. Issue can be mitigated through mobile application updates. Device firmware remains unchanged.

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 confidence

The TP-Link Tapo mobile application for iOS and Android contains an unauthenticated API endpoint that returns password hashes for Tapo cameras. An attacker on the local network can intercept these exposed hashes and perform offline brute force attacks to recover the plaintext passwords.

MitigationUpdate the TP-Link Tapo mobile application to the latest version available in the App Store or Google Play Store to receive the security patch that addresses the exposed password hash vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Adjacent
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Tapo mobile app is installed
    On Android, go to Settings > Apps > Tapo; on iOS, go to Settings > General > iPhone Storage > Tapo to see if the application is installed
    Affected if The Tapo mobile application is present on the device
  2. Check the installed Tapo app version
    On Android, view the app info screen in Settings > Apps > Tapo to see the version number; on iOS, view the App Store listing or check the app version in iPhone Storage settings
    Affected if The installed version matches or falls within the affected version range (compare your version to the known vulnerable versions)
  3. Determine if Tapo cameras are registered with the app
    Open the Tapo app and check if any camera devices are added/configured in the app's device list
    Affected if Tapo cameras are paired and registered to the mobile app, making the password hashes potentially accessible
  4. Assess local network exposure
    Check if the device running the Tapo app and the Tapo cameras are on a shared local network that could be accessed by untrusted parties (e.g., public Wi-Fi, shared networks)
    Affected if The mobile device and cameras communicate over a network accessible to untrusted users, allowing interception of the vulnerable API responses

The user is affected if the Tapo mobile app version is within the vulnerable range AND Tapo cameras are registered to the app AND an untrusted party could access the local network to intercept API responses containing password hashes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the TP-Link Tapo mobile application to the latest version available in the App Store or Google Play Store to receive the security patch that addresses the exposed password hash vulnerability.

Recommended fix Moderate confidence
  1. Open the App Store (iOS) or Google Play Store (Android) on your mobile device
  2. Search for "TP-Link Tapo" or "Tapo - Smart Home","Locate the Tapo camera app in the search results
  3. Check if an update is available. If an update is available, tap "Update" to install the latest version
  4. Alternatively, enable automatic app updates in your device settings to ensure you receive future security patches
  5. After updating, verify the app version in your device's app settings to confirm the update was applied

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14553 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14553 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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