# CVE-2025-8627: Unauthenticated Protocol Commands on TP-Link KP303

> Unauthenticated protocol commands on TP-Link KP303 smart plugs allow attackers to cause power-offs and leak information.

- **Severity:** High 8.7 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2025
- **Updated:** 26 Aug 2025
- **Also known as:** GHSA-mjmv-2pj5-x57j

## What is CVE-2025-8627?

CVE-2025-8627 is a high-severity missing authorization vulnerability in TP-Link KP303 (US) Smartplug, published on 25 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2025-8627?

It affects 1 product.


Products: Tp-Link Kp303 Firmware.

## How do I fix CVE-2025-8627?

No fix has been published for CVE-2025-8627 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-8627 being exploited?

There is no known exploitation of CVE-2025-8627 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-8627 and fix it if it is affected.

What it is: CVE-2025-8627 is a high-severity missing authorization vulnerability in TP-Link KP303 (US) Smartplug, published on 25 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-8627 in the wild and no public exploit code.

Affected product: TP-Link KP303 (US) Smartplug. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-8627/ (Markdown: https://insights.sbomify.com/CVE-2025-8627/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-8627
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-8627
- OSV: https://osv.dev/vulnerability/CVE-2025-8627

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-8627/
Summaries are generated and may contain mistakes; the official description above is the record.