# CVE-2025-15371: Tenda i24 Shadow File hard-coded credentials

> Hard-coded credentials in the shadow file allow local attackers to bypass authentication and gain elevated privileges on Tenda network devices.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Dec 2025
- **Updated:** 2 Jan 2026
- **Also known as:** GHSA-9qhr-gr34-rmgj

## What is CVE-2025-15371?

CVE-2025-15371 is a high-severity vulnerability in Tenda 4G03 Pro, published on 31 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability has been found in Tenda i24, 4G03 Pro, 4G05, 4G08, G0-8G-PoE, Nova MW5G and TEG5328F up to 65.10.15.6. Affected is an unknown function of the component Shadow File. Such manipulation with the input Fireitup leads to hard-coded credentials. An attack has to be approached locally. The exploit has been disclosed to the public and may be used.

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

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


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

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

## Is CVE-2025-15371 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15371 is a high-severity vulnerability in Tenda 4G03 Pro, published on 31 Dec 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-15371 in the wild and no public exploit code.

Affected product: Tenda 4G03 Pro. 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-15371/ (Markdown: https://insights.sbomify.com/CVE-2025-15371/index.md)
```

## Sources

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

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