dbcve.org
CWE-330Weakness · CWE-330

CVE-2025-13955

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 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.

NVD · unedited
Predictable default Wi-Fi Password in Access Point functionality in EZCast Pro II before version 1.17478.177 allows attackers in Wi-Fi range to gain access to the dongle by calculating the default password from observable device identifiers

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.

dbcve analysis · high confidence

The EZCast Pro II dongle uses a default Wi-Fi password for its Access Point functionality that can be derived from observable device identifiers. Attackers within Wi-Fi range can capture these identifiers and calculate the password, gaining unauthorized access to the device.

MitigationUpdate EZCast Pro II to firmware version 1.17478.177 or later, and change the default Wi-Fi password to a strong, unique password that is not derived from device identifiers.

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

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.

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:N/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? 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.

dbcve checks

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

  1. Identify the device model
    Check if the device is an EZCast Pro II dongle. This is typically visible on the device packaging, on a label attached to the device itself, or by connecting to the device's web interface and checking the device information page.
    Affected if The device is an EZCast Pro II dongle.
  2. Check the firmware version
    Connect to the EZCast Pro II web interface (usually at 192.168.1.1 or via the EZCast app), navigate to the Settings or Device Info section, and record the firmware version displayed.
    Affected if The firmware version is lower than 1.17478.177 (for example, 1.x versions prior to 1.17478).
  3. Verify the Access Point password configuration
    Log into the device web interface, go to the Wi-Fi or Access Point settings, and examine whether the current Wi-Fi password matches a default pattern derived from device identifiers (such as MAC address or serial number). If the password is set to a default or easily guessable format based on visible device labels, this indicates the vulnerability.
    Affected if The Wi-Fi password is the default password or appears to be derived from device identifiers (MAC address, serial number) rather than a strong, unique password set by the user.
  4. Check for recent firmware updates
    In the device settings or via the EZCast mobile application, check if any firmware updates are available or have been applied. Look for update history or current version information.
    Affected if The device shows no available updates or the last update was applied before version 1.17478.177.

The environment is affected if an EZCast Pro II dongle is in use with firmware version below 1.17478.177 and the Wi-Fi Access Point password is still set to the default derived from device identifiers.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update EZCast Pro II to firmware version 1.17478.177 or later, and change the default Wi-Fi password to a strong, unique password that is not derived from device identifiers.

Recommended fix Moderate confidence

EZCast Pro II firmware version 1.17478.177 or later

  1. 1. Identify all EZCast Pro II devices on the network
  2. 2. Check the current firmware version of each device through the device management interface
  3. 3. Navigate to the vendor's official support or firmware download page (typically found on the vendor's website or through the EZCast application)
  4. 4. Download firmware version 1.17478.177 or later
  5. 5. Follow the vendor's official firmware update procedure to flash the new firmware to each device
  6. 6. After updating, verify the new firmware version is installed correctly
  7. 7. Change the default Wi-Fi password to a strong, unique password if it was not automatically randomized by the update
Caveat Review vendor release notes for any functionality changes or configuration requirements before updating

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13955 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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