Hard-coded CredentialsWeakness · CWE-798

CVE-2025-13954

CRITICAL · 9.3 CVSS v4.0 Published 2025-12-10

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

98/100

Remediation priority · Urgent

No privileges Zero-click

Official description

NVD · unedited

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

Technical summary

dbcve analysis · high confidence

Hard-coded cryptographic keys are embedded in the Admin UI of EZCast Pro II devices prior to version 1.17478.177. Attackers who discover these keys can use them to bypass authentication and authorization mechanisms, gaining full administrative access to the device's web interface.

MitigationUpgrade EZCast Pro II firmware to version 1.17478.177 or later to replace the hard-coded cryptographic keys with properly generated, unique keys. If upgrading is not immediately possible, restrict network access to the admin UI interface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Adjacent
Complexity: Low
Privileges: None
Authentication: Y
User interaction: None
Scope: X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:X/V:X/RE:L/U:X

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify the device model

Access the device admin interface or check the device label/packaging to confirm the model is EZCast Pro II

Affected if The device is not an EZCast Pro II model
Determine the installed firmware version

Log into the admin UI and navigate to the System or Settings page to find the firmware version information, or use the device's mobile app if available

Affected if Unable to retrieve the firmware version from the device
Compare firmware version to the fixed release

Check if the installed firmware version is below 1.17478.177. If the version is equal to or higher than 1.17478.177, the hard-coded keys have been replaced.

Affected if Firmware version is lower than 1.17478.177 (e.g., 1.17478.176 or earlier)
Assess admin interface accessibility

Determine if the admin web interface (typically on port 80/443 or a vendor-specific port) is reachable from untrusted networks. Check firewall rules, NAT configurations, or VPN policies.

Affected if The admin interface is accessible from networks outside the trusted administrative zone

If the device is an EZCast Pro II running firmware versions before 1.17478.177 and the admin interface is network-accessible, the environment is vulnerable to CVE-2025-13954.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Upgrade EZCast Pro II firmware to version 1.17478.177 or later to replace the hard-coded cryptographic keys with properly generated, unique keys. If upgrading is not immediately possible, restrict network access to the admin UI interface.

Recommended fix Moderate confidence

EZCast Pro II firmware version 1.17478.177 or later

1. Identify the specific EZCast Pro II device model and current firmware version
2. Download the latest firmware version 1.17478.177 or later from the official vendor source
3. Access the device admin UI or use the vendor's firmware update mechanism
4. Upload and apply the firmware update following vendor instructions
5. After reboot, verify the device is running version 1.17478.177 or later
6. Confirm the admin UI authorization bypass vulnerability is resolved by testing access controls

Caveat Review vendor release notes for any configuration or feature changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory

Consultation2.0 h
Implementation1.0 h
Testing2.0 h
Review / QA1.0 h

6.0 hours of engineering $1,060

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2025-13954 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13954 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2025-13954?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsA vendor remedy is published

Severity 9.3 Critical

Exploit likelihood EPSS, next 30 days 0.2%

Remediation

A high-priority fix

Have this fixed 6 hrs · Low

Typical engagement from $1,060

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2025-13954 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References