Live ChatWordPress extension · 3cx
CVE-2017-2187
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 · uneditedCross-site scripting vulnerability in WP Live Chat Support prior to version 7.0.07 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.
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 confidenceCross-site scripting (XSS) vulnerability in the WP Live Chat Support WordPress plugin versions prior to 7.0.07 allows remote attackers to inject arbitrary JavaScript or HTML through unspecified input vectors. The vulnerability stems from insufficient input sanitization in the chat functionality, enabling malicious scripts to execute in the context of other users' browsers.
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
<= 7.0.06CVSS 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.
-
Confirm WP Live Chat Support plugin is installedNavigate to WordPress admin dashboard > Plugins, or inspect the /wp-content/plugins/ directory for the 'wp-live-chat-support' folderAffected if The plugin folder exists in the WordPress installation
-
Identify installed plugin versionIn WordPress Plugins admin page, locate 'WP Live Chat Support' and read the version number displayed beneath the plugin name; alternatively, open /wp-content/plugins/wp-live-chat-support/readme.txt and check the version in the headerAffected if Version is lower than 7.0.07 (for example, 7.0.06, 7.0.05, etc.)
-
Check if 3cx Live Chat is installedInspect /wp-content/plugins/ directory for a '3cx-live-chat' folder, or check WordPress Plugins page for a 3cx Live Chat entryAffected if 3cx Live Chat is present with version 7.0.06 or earlier
-
Determine if chat functionality is activeAccess the plugin settings at Settings > Live Chat Support, or check if the chat widget shortcode [lgc_chat] or live chat block is deployed on any pages/postsAffected if Chat feature is enabled and the chat interface is accessible to website visitors
User is affected if WP Live Chat Support version is below 7.0.07 OR 3cx Live Chat version 7.0.06 or lower is installed AND the chat functionality is enabled and accessible on the site.
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 dataUpgrade WP Live Chat Support to version 7.0.07 or later. If immediate upgrading is not feasible, disable the plugin until the patch can be applied. Additionally, implement Web Application Firewall (WAF) rules as a compensating control.
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-2017-2187 — 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-2017-2187 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