# CVE-2025-52364: Misconfiguration in n/a

> Insecure default configuration enables remote telnet access, allowing attackers to execute commands on the device.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2025
- **Updated:** 14 Jul 2025
- **Also known as:** GHSA-m3g5-6w39-wjj8

## What is CVE-2025-52364?

CVE-2025-52364 is a high-severity vulnerability in n/a, published on 9 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Insecure Permissions vulnerability in Tenda CP3 Pro Firmware V22.5.4.93 allows the telnet service (telnetd) by default at boot via the initialization script /etc/init.d/eth.sh. This allows remote attackers to connect to the device s shell over the network, potentially without authentication if default or weak credentials are present

Weakness: CWE-1391 (Use of Weak Credentials)

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

It affects 1 product.


Products: Tenda Cp3 Pro Firmware.

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

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

## Is CVE-2025-52364 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-52363](https://insights.sbomify.com/CVE-2025-52363/): Hardcoded credentials in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-52364 is a high-severity vulnerability in n/a, published on 9 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-52364 in the wild and no public exploit code.

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-52364/ (Markdown: https://insights.sbomify.com/CVE-2025-52364/index.md)
```

## Sources

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

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