# CVE-2025-13954: Hard-coded cryptographic keys in EZCast Pro II Dongle

> Attackers can bypass authorization and gain full admin access to EZCast Pro II Dongles due to hard-coded cryptographic keys.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:H/SA:N/AU:Y/RE:L`)
- **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:** 10 Dec 2025
- **Updated:** 28 May 2026
- **Also known as:** GHSA-2qcw-cw26-gchc

## What is CVE-2025-13954?

CVE-2025-13954 is a critical vulnerability in EZCast Pro II, published on 10 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Hard-coded cryptographic keys in Admin UI of EZCast Pro II before version 1.17478.177 allows attackers to bypass authorization checks and gain full access to the admin UI

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

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


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

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

## Is CVE-2025-13954 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13954 is a critical vulnerability in EZCast Pro II, published on 10 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-13954 in the wild and no public exploit code.

Affected product: EZCast Pro II. 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-13954/ (Markdown: https://insights.sbomify.com/CVE-2025-13954/index.md)
```

## Sources

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

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