dbcve.org
Videowhisper Live Streaming IntegrationWordPress extension · Videowhisper

CVE-2014-1905

HIGH · 10.0 CVSS v2.0 Published 2014-12-29
Fix available
A fix is available. Upgrade to after 4.27.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable 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
Unrestricted file upload vulnerability in ls/vw_snapshots.php in the VideoWhisper Live Streaming Integration plugin before 4.29.5 for WordPress allows remote attackers to execute arbitrary PHP code by uploading a file with a double extension, and then accessing the file via a direct request to a wp-content/plugins/videowhisper-live-streaming-integration/ls/snapshots/ pathname, as demonstrated by a .php.jpg filename.

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

Unrestricted file upload vulnerability in ls/vw_snapshots.php in the VideoWhisper Live Streaming Integration plugin for WordPress allows remote attackers to upload files with double extensions (e.g., .php.jpg), which are then executed as PHP code when accessed directly in the snapshots directory.

MitigationUpgrade to VideoWhisper Live Streaming Integration plugin version 4.29.5 or later, and review the snapshots upload directory for any malicious .php files that may have been uploaded.

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
Videowhisper Live Streaming IntegrationWordPress extension
Affected:<= 4.27.4

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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. Confirm plugin installation and version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and locate VideoWhisper Live Streaming Integration. Check the version number displayed. Compare your installed version against the affected range: <= 4.27.4
    Affected if The plugin version is 4.27.4 or lower
  2. Locate the vulnerable PHP file
    Check your WordPress plugin directory (wp-content/plugins/live-streaming-integration/) for the presence of ls/vw_snapshots.php
    Affected if The file ls/vw_snapshots.php exists in the plugin directory
  3. Inspect the snapshots upload directory
    Examine the wp-content/plugins/live-streaming-integration/snapshots/ directory via FTP or file manager. Look for files with double extensions like .php.jpg, .php.png, or any .php files that you did not intentionally upload
    Affected if The snapshots directory contains any .php files or files with PHP-like double extensions (e.g., shell.php.jpg)
  4. Verify web accessibility of snapshots directory
    Attempt to access the snapshots directory directly via web browser (e.g., https://yoursite.com/wp-content/plugins/live-streaming-integration/snapshots/)
    Affected if The snapshots directory is directly accessible and lists or serves files

You are affected if the VideoWhhisper Live Streaming Integration plugin version is 4.27.4 or lower AND the snapshots directory contains any executable PHP files or is directly accessible via the web.

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
Upgrade available Upgrade to a release after 4.27.4
Interim mitigation

Upgrade to VideoWhisper Live Streaming Integration plugin version 4.29.5 or later, and review the snapshots upload directory for any malicious .php files that may have been uploaded.

Recommended fix High confidence

4.29.5 or later

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to the WordPress admin dashboard > Plugins > Installed Plugins
  3. 3. Find the Videowhisper Live Streaming Integration plugin
  4. 4. Click Update Now to install the latest version (4.29.5 or later)
  5. 5. Alternatively, upload the plugin manually by downloading version 4.29.5 or newer from the WordPress plugin repository
  6. 6. After updating, verify the plugin version shows 4.29.5 or higher under Plugins > Installed Plugins
  7. 7. Audit the wp-content/plugins/videowhisper-live-streaming-integration/ls/snapshots/ directory for any suspicious .php files or unexpected file extensions and remove any malicious uploads
  8. 8. Review WordPress access logs for any suspicious requests to the snapshots directory

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

Fix this in Videowhisper Live Streaming Integration 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 the upgrade done

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-2014-1905 — 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-2014-1905 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