# CVE-2025-52363: Hardcoded credentials in n/a

> An attacker with firmware access can extract hardcoded root credentials to gain administrative control over the device.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:L/A: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:** 14 Jul 2025
- **Updated:** 14 Jul 2025
- **Also known as:** GHSA-j52h-9ppw-g36v

## What is CVE-2025-52363?

CVE-2025-52363 is a medium-severity vulnerability in n/a, published on 14 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Tenda CP3 Pro Firmware V22.5.4.93 contains a hardcoded root password hash in the /etc/passwd file and /etc/passwd-. An attacker with access to the firmware image can extract and attempt to crack the root password hash, potentially obtaining administrative access

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Tenda Cp3 Pro Firmware.

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

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

## Is CVE-2025-52363 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-52364](https://insights.sbomify.com/CVE-2025-52364/): Misconfiguration in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-52363 is a medium-severity vulnerability in n/a, published on 14 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52363 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-52363/ (Markdown: https://insights.sbomify.com/CVE-2025-52363/index.md)
```

## Sources

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

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