dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-24937

HIGH · 7.2 CVSS v3.1 Published 2026-05-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
Improper Control of Generation of Code ('Code Injection') vulnerability in VideoWhisper.Com Broadcast Live Video allows Code Injection. This issue affects Broadcast Live Video: from n/a before 7.1.3.

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

Code injection vulnerability in VideoWhisper Broadcast Live Video allows remote attackers to inject and execute arbitrary code through improper handling of user input. The vulnerability exists in versions before 7.1.3 and likely involves insufficient input validation or sanitization of data that gets processed as executable code.

MitigationUpgrade to Broadcast Live Video version 7.1.3 or later to obtain the security patch for this vulnerability.

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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 if VideoWhisper Broadcast Live Video plugin is installed
    Check your CMS plugins or extensions directory for the VideoWhisper Broadcast Live Video plugin. Common locations include /wp-content/plugins/ for WordPress or similar plugin directories in other CMS platforms.
    Affected if The plugin files are present in the system
  2. Determine the installed version of the VideoWhisper plugin
    Look for a version file, readme.txt, or plugin header metadata that specifies the version number. Common paths include the plugin main PHP file or a separate version.xml/changelog file within the plugin directory.
    Affected if The version is lower than 7.1.3 (all versions before this fix are vulnerable)
  3. Verify the plugin is active and accessible
    Check if the plugin is enabled in your CMS admin panel or if the plugin files are being served via the web server.
    Affected if The plugin is active and processing user requests
  4. Check for exposed input parameters related to broadcast functionality
    Review your web server logs and application code for requests to VideoWhisper endpoints that accept user-supplied data, especially parameters that could be used in code generation contexts.
    Affected if User input is directly used in contexts that could lead to code execution

A system is affected if the VideoWhisper Broadcast Live Video plugin is installed with a version lower than 7.1.3 and the plugin is active.

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

Upgrade to Broadcast Live Video version 7.1.3 or later to obtain the security patch for this vulnerability.

Recommended fix Moderate confidence

Version 7.1.3 or latest stable release of VideoWhisper Broadcast Live Video

  1. Create a complete backup of your WordPress site and database before making any changes
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Locate the VideoWhisper Broadcast Live Video plugin
  4. Check if an update to version 7.1.3 or later is available and install it
  5. Alternatively, download version 7.1.3 or the latest stable version from the official VideoWhisper repository or your licensed source
  6. After updating, verify the plugin version in the plugins list to confirm the update was successful
  7. Test that the video broadcasting functionality works correctly
  8. Review any changelog or release notes for additional configuration requirements

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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