Live ChatWordPress extension · 3cx
CVE-2019-14950
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 · uneditedThe wp-live-chat-support plugin before 8.0.27 for WordPress has XSS via the GDPR 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 · moderate confidenceThe wp-live-chat-support WordPress plugin before version 8.0.27 contains a cross-site scripting (XSS) vulnerability on its GDPR compliance page. Attackers can inject malicious JavaScript code through unsanitized user input on this page, which then executes in the browsers of site visitors or administrators viewing the page.
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
Live ChatWordPress extension
< 8.0.27CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and locate '3cx Live Chat' or 'wp-live-chat-support'. The version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file for a version constant, or inspect the plugin header in /wp-content/plugins/live-chat-wp/ folder.Affected if The displayed version is lower than 8.0.27 (e.g., 8.0.26, 8.0.25, etc.)
-
Locate the GDPR compliance pageIn WordPress admin, navigate to the plugin settings. Look for a menu item labeled 'GDPR', 'Privacy', or 'Compliance' within the Live Chat plugin menu. The URL typically contains 'gdpr' or 'privacy'. Alternatively, access the page directly by appending '?page=wplivechat-menu-gdpr' to your site URL.Affected if The GDPR compliance page exists and is accessible in the admin dashboard
-
Verify the plugin is activeConfirm the 3cx Live Chat / wp-live-chat-support plugin is currently activated in Plugins > Installed Plugins. An inactive plugin with a vulnerable version would not be exploitable.Affected if The plugin is activated and running on the WordPress site
You are affected if the 3cx Live Chat plugin version is below 8.0.27 AND the plugin is active with the GDPR compliance page accessible in the WordPress admin.
Generated from the published advisory. Verify against your own configuration.
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 data8.0.27
Update the wp-live-chat-support plugin to version 8.0.27 or later to obtain the security fix. Before updating, create a full backup of the WordPress site and test the update in a staging environment to ensure compatibility with existing chat functionality.
Fix this in Live Chat
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14950 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-14950 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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