dbcve.org
Ezcast Pro Dongle Ii FirmwareOperating system · Nimbletech

CVE-2026-24345

HIGH · 8.8 CVSS v3.1 Published 2026-01-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery in Admin UI of EZCast Pro II version 1.17478.146 allows attackers to bypass authorization checks and gain full access to the admin UI

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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the admin web interface of EZCast Pro II version 1.17478.146 allows remote attackers to trick authenticated administrators into unknowingly executing unauthorized administrative actions. The application's admin UI lacks proper anti-CSRF token validation or Origin/Referer header checks, enabling attackers to bypass authorization and gain full admin access.

MitigationImplement anti-CSRF tokens for all state-changing admin operations, validate Origin and Referer headers server-side, and configure SameSite attributes for session cookies. Apply firmware updates from vendor when available.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ezcast Pro Dongle Ii FirmwareOperating system
Affected:= 1.17478.146

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 and firmware version
    Access the admin web interface of the EZCast Pro II device and navigate to System Settings or About page to view the firmware version. Alternatively, check the device label or use the device's discovery app to retrieve firmware information.
    Affected if The firmware version is exactly 1.17478.146
  2. Confirm admin web interface is accessible
    Verify that the admin web interface is reachable on the local network by accessing the device's IP address via HTTP/HTTPS (typically ports 80 or 443).
    Affected if The admin web interface is exposed and accessible on the network
  3. Check for anti-CSRF token presence
    Log into the admin interface and inspect the HTML source of state-changing forms (such as network settings, user management, or firmware update). Look for hidden input fields containing CSRF tokens or similar security tokens. Submit a form and capture the request to see if a token parameter is sent.
    Affected if No anti-CSRF tokens are found in admin forms, or the tokens are missing from state-changing requests
  4. Inspect Origin and Referer header handling
    Use a web proxy to intercept admin interface requests. Observe whether the server validates the Origin or Referer headers by sending requests with missing or mismatched headers. Check if the server accepts such requests without rejecting them.
    Affected if The server accepts requests without validating Origin or Referer headers, or returns success responses to requests with altered/missing headers
  5. Check session cookie SameSite attribute
    Using browser developer tools or a proxy, inspect the session cookies set by the admin interface. Examine the Set-Cookie headers to see if the SameSite attribute is configured, and if so, which value is used (Strict, Lax, or None).
    Affected if Session cookies lack SameSite attribute or have it set to None without secure flag

A user is affected if they are running firmware version 1.17478.146 on a Nimbletech EZCast Pro II device with an accessible admin interface that lacks anti-CSRF tokens and proper Origin/Referer header validation.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens for all state-changing admin operations, validate Origin and Referer headers server-side, and configure SameSite attributes for session cookies. Apply firmware updates from vendor when available.

Fix this in Ezcast Pro Dongle Ii Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24345 — 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-2026-24345 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