# CVE-2025-56675: Information disclosure in video doorbell T6

> The EKEN video doorbell leaks sensitive Wi-Fi credentials to cloud servers via debug logs, exposing network access details to potential attackers.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Sep 2025
- **Updated:** 30 Sep 2025
- **Also known as:** GHSA-jwvx-8mrf-4v7m

## What is CVE-2025-56675?

CVE-2025-56675 is a low-severity vulnerability in EKEN video doorbell T6, published on 30 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The EKEN video doorbell T6 BT60PLUS_MAIN_V1.0_GC1084_20230531 periodically sends debug logs to the EKEN cloud servers with sensitive information such as the Wi-Fi SSID and password.

Weakness: CWE-669 (Incorrect Resource Transfer Between Spheres)

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


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

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

## Is CVE-2025-56675 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-56675 is a low-severity vulnerability in EKEN video doorbell T6, published on 30 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-56675 in the wild and no public exploit code.

Affected product: EKEN video doorbell T6. 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-56675/ (Markdown: https://insights.sbomify.com/CVE-2025-56675/index.md)
```

## Sources

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

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