# CVE-2025-25680: Code injection in n/a

> Attackers can execute arbitrary code on LSC Smart Connect cameras by presenting a specially crafted QR code during Wi-Fi configuration.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Mar 2025
- **Updated:** 21 Mar 2025
- **Also known as:** GHSA-5hc5-9qwg-w899

## What is CVE-2025-25680?

CVE-2025-25680 is a high-severity code injection vulnerability in n/a, published on 11 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

LSC Smart Connect LSC Indoor PTZ Camera 7.6.32 is contains a RCE vulnerability in the tuya_ipc_direct_connect function of the anyka_ipc process. The vulnerability allows arbitrary code execution through the Wi-Fi configuration process when a specially crafted QR code is presented to the camera.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Lsc Ptz Dual Band Camera Firmware.

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

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

## Is CVE-2025-25680 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25680 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-25680 is a high-severity code injection vulnerability in n/a, published on 11 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25680 exists.

Affected product: n/a. 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-25680/ (Markdown: https://insights.sbomify.com/CVE-2025-25680/index.md)
```

## Sources

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

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