dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-9644

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
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
The LiveSmart Video Chat Live Video Chat plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'livesmart_widget' shortcode in all versions up to, and including, 1.2 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 LiveSmart Video Chat WordPress plugin versions up to 1.2 suffer from a stored XSS vulnerability in the livesmart_widget shortcode. Authenticated users with contributor-level permissions can inject malicious JavaScript via unsanitized shortcode attributes; the payload persists in the database and executes whenever users view affected pages.

MitigationUpdate the plugin to a version beyond 1.2 that includes proper input sanitization and output escaping; if no patched version exists, remove the plugin or audit/cleanse any existing shortcode entries in the database.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Identify if LiveSmart Video Chat plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'livesmart-video-chat' or similar, or use WP CLI: wp plugin list --search=livesmart
    Affected if The plugin folder exists in the plugins directory
  2. Determine the installed plugin version
    Open the main plugin PHP file (usually livesmart-video-chat.php or similar in the plugin folder) and locate the Version header in the plugin comment block, or run: wp plugin get livesmart-video-chat --format=version
    Affected if The version number is 1.2 or lower
  3. Search for livesmart_widget shortcode usage in content
    Query the WordPress database: SELECT ID, post_title FROM wp_posts WHERE post_content LIKE '%[livesmart_widget%' AND post_status IN ('publish', 'draft', 'pending'); or use WP CLI: wp post list --s='[livesmart_widget'
    Affected if Any posts or pages contain the livesmart_widget shortcode
  4. Inspect shortcode attributes in database for unsanitized input
    Examine the post_content field for any shortcode entries found: look for unusual characters, script tags, or javascript: URLs within attribute values like [livesmart_widget some_attr='<script>...
    Affected if Shortcode entries contain raw HTML, script tags, or JavaScript event handlers in attribute values
  5. Verify user role permissions
    Check if any contributor-level users exist: wp user list --role=contributor or query wp_usermeta for wp_capabilities containing 'contributor'
    Affected if Contributor-level or higher authenticated users exist on the site

A user is affected if the LiveSmart Video Chat plugin version is 1.2 or lower AND the livesmart_widget shortcode is present in any published content with unsanitized attribute values that could contain malicious scripts.

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 the plugin to a version beyond 1.2 that includes proper input sanitization and output escaping; if no patched version exists, remove the plugin or audit/cleanse any existing shortcode entries in the database.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (version higher than 1.2)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'LiveSmart Video Chat' plugin
  4. Check if an update is available and update to the latest version
  5. Alternatively, download the latest version from the WordPress plugin repository (plugins.trac.wordpress.org) and upload via Plugins > Add New > Upload Plugin

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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