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

> Attackers can gain root access to H3C devices using default credentials, leading to privilege escalation and potential code execution.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Sep 2025
- **Updated:** 19 Sep 2025
- **Also known as:** GHSA-h963-6gvx-2vg6

## What is CVE-2025-57295?

CVE-2025-57295 is a high-severity vulnerability in n/a, published on 18 Sep 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

H3C devices running firmware version NX15V100R015 are vulnerable to unauthorized access due to insecure default credentials. The root user account has no password set, and the H3C user account uses the default password "admin," both stored in the /etc/shadow file. Attackers with network access can exploit these credentials to gain unauthorized root-level access to the device via the administrative interface or other network services, potentially leading to privilege escalation, information disclosure, or arbitrary code execution.

Weakness: CWE-521 (Weak Password Requirements), CWE-1188 (Initialization of a Resource with an Insecure Default)

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

It affects 1 product.


Products: H3c Magic Nx15 Firmware.

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

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

## Is CVE-2025-57295 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-57295 is a high-severity vulnerability in n/a, published on 18 Sep 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-57295 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-57295/ (Markdown: https://insights.sbomify.com/CVE-2025-57295/index.md)
```

## Sources

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

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