dbcve.org
Videowhisper Live Streaming IntegrationWordPress extension · Videowhisper

CVE-2014-2297

MEDIUM · 6.1 CVSS v3.0 Published 2018-03-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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
Multiple cross-site scripting (XSS) vulnerabilities in the VideoWhisper Live Streaming Integration plugin 4.29.6 for WordPress allow remote attackers to inject arbitrary web script or HTML via the (1) n parameter to ls/htmlchat.php or (2) bgcolor parameter to ls/index.php. NOTE: vector 1 may overlap CVE-2014-1906.4.

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 VideoWhisper Live Streaming Integration plugin 4.29.6 for WordPress contains reflected cross-site scripting (XSS) vulnerabilities in two scripts. The 'n' parameter in ls/htmlchat.php and the 'bgcolor' parameter in ls/index.php accept user-supplied input without proper sanitization or output encoding, allowing attackers to inject arbitrary JavaScript or HTML that executes in the context of the victim's browser.

MitigationUpdate to a patched version of the VideoWhisper plugin if available; otherwise, implement proper input validation and output encoding on the affected parameters (n and bgcolor) in both ls/htmlchat.php and ls/index.php, or deploy a WAF rule to block XSS payloads in these parameters.

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

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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. Locate the VideoWhisper plugin installation directory
    Check the wp-content/plugins/ directory for a folder named 'videowhisper-live-streaming-integration' or similar variant
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually named plugin-name.php in the plugin folder) and locate the version comment in the file header, or check the WordPress plugin admin page for the installed version number
    Affected if The reported version is exactly 4.29.6
  3. Verify vulnerable script files exist
    Check for the presence of ls/htmlchat.php and ls/index.php within the plugin directory
    Affected if These specific PHP files exist in the ls subfolder of the plugin
  4. Confirm the parameter acceptance (optional manual test)
    Review the source code of ls/htmlchat.php for use of the 'n' parameter without sanitization, and ls/index.php for the 'bgcolor' parameter without encoding
    Affected if The code reads the parameter directly from request (e.g., $_GET['n'] or $_GET['bgcolor']) and outputs it without htmlspecialchars or similar encoding

If the VideoWhisper Live Streaming Integration plugin version 4.29.6 is installed with the ls/htmlchat.php and ls/index.php scripts present, the environment is affected by this reflected XSS vulnerability.

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

Update to a patched version of the VideoWhisper plugin if available; otherwise, implement proper input validation and output encoding on the affected parameters (n and bgcolor) in both ls/htmlchat.php and ls/index.php, or deploy a WAF rule to block XSS payloads in these parameters.

Fix this in Videowhisper Live Streaming Integration 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-2014-2297 — 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-2297 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