dbcve.org
Kp303 FirmwareOperating system · Tp Link

CVE-2025-8627

HIGH · 8.8 CVSS v3.1 Published 2025-08-25
Fix available
A fix is available. Upgrade to 1.1.0 or later.
See remediation →
93/100
Remediation priority · Urgent
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
The TP-Link KP303 Smartplug can be issued unauthenticated protocol commands that may cause unintended power-off condition and potential information leak. This issue affects TP-Link KP303 (US) Smartplug: before 1.1.0.

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 · high confidence

The TP-Link KP303 Smartplug contains an authentication bypass vulnerability allowing unauthenticated attackers to send protocol commands that can trigger unintended power-off conditions and potentially leak sensitive information. This affects versions prior to 1.1.0.

MitigationUpdate TP-Link KP303 (US) firmware to version 1.1.0 or later. If patching is not immediately feasible, network-segment the device and monitor for unauthorized power-state commands.

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
Kp303 FirmwareOperating system
Affected:< 1.1.0

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
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 the device model
    Locate the physical smart plug or check the TP-Link Kasa app for connected devices. Confirm the model number displayed is KP303.
    Affected if The device is a TP-Link KP303 unit.
  2. Determine the installed firmware version
    Open the TP-Link Kasa mobile app, select the KP303 device, go to Device Settings, and look for the Firmware Version field. Alternatively, access the device via its web interface if available and check the firmware information.
    Affected if The firmware version cannot be verified or is displayed as anything prior to 1.1.0.
  3. Compare version against the vulnerability threshold
    Document the exact firmware version string found and compare it numerically to 1.1.0. Any version below 1.1.0 (such as 1.0.4, 1.0.8, etc.) is within the affected range.
    Affected if The installed firmware version is less than 1.1.0.
  4. Assess network exposure
    Check if the KP303 device is directly accessible from the internet or on a shared network segment with untrusted devices. Review router/firewall rules for port forwarding to the device's IP or any ACLs allowing external access to the device.
    Affected if The device is reachable from untrusted networks without network segmentation.

You are affected if the device is a TP-Link KP303 running firmware version lower than 1.1.0 and is network-accessible to untrusted parties.

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
Upgrade available Upgrade to 1.1.0 or later
Fixed in 1.1.0
Interim mitigation

Update TP-Link KP303 (US) firmware to version 1.1.0 or later. If patching is not immediately feasible, network-segment the device and monitor for unauthorized power-state commands.

Recommended fix Moderate confidence

1.1.0

  1. Open the TP-Link Kasa app on your mobile device
  2. Navigate to the KP303 Smartplug device settings
  3. Check the current firmware version under Device Info or Settings
  4. If firmware version is below 1.1.0, look for a firmware update option within the app
  5. If an update is available, ensure the smartplug remains powered and connected during the update process
  6. Follow the in-app prompts to download and install firmware version 1.1.0
  7. After the update completes, verify the new firmware version is 1.1.0

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

Fix this in Kp303 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8627 — 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-8627 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