Click to Chat at a glance
- 5 publicly disclosed vulnerabilities, 2 of them rated High or Critical. The most recent was disclosed on Oct 13, 2026.
- Ranked #93 by popularity on WordPress.org (600,000+ active installs).
- The latest version is 4.47 (released Nov 17, 2026). The most recent security fix shipped in 4.45.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your Click to Chat version
Enter the Click to Chat version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “Click to Chat”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Click to Chat”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (4.47). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known Click to Chat vulnerabilities
Click to Chat <= 4.44 - Unauthenticated Arbitrary Shortcode Execution via REQUEST_URI via {url} Placeholder
Other weakness · CVE-2026-92097
Affected versions: ≤ 4.44
Fixed in: 4.45
Severity: Critical 9.1 · Disclosed Oct 13, 2026
Click to Chat <= 4.39 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'num' Shortcode Parameter
Cross-site scripting (XSS) · CVE-2026-7795
Affected versions: ≤ 4.39
Fixed in: 4.40
Severity: Medium 6.4 · Disclosed Jun 5, 2026
Click to Chat <= 4.22 - Authenticated (Contributor+) Stored DOM-Based Cross-Site Scripting via data-no_number Parameter
Cross-site scripting (XSS) · CVE-2025-5336
Affected versions: ≤ 4.22
Fixed in: 4.23
Severity: Medium 6.4 · Disclosed Jun 13, 2025
Click to Chat – HoliThemes <= 3.35 - Authenticated (Contributor+) Local File Inclusion
Arbitrary file read or deletion · CVE-2024-3849
Affected versions: ≤ 3.35
Fixed in: 4.0
Severity: High 8.8 · Disclosed Apr 17, 2024
Click to Chat <= 3.18 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode
Cross-site scripting (XSS) · CVE-2022-4480
Affected versions: ≤ 3.18
Fixed in: 3.18.1
Severity: Medium 6.4 · Disclosed Dec 21, 2022
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| Click to Chat <= 4.44 - Unauthenticated Arbitrary Shortcode Execution via REQUEST_URI via {url} PlaceholderOther weakness · CVE-2026-92097 | ≤ 4.44 | 4.45 | Critical 9.1 | Oct 13, 2026 |
| Click to Chat <= 4.39 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'num' Shortcode ParameterCross-site scripting (XSS) · CVE-2026-7795 | ≤ 4.39 | 4.40 | Medium 6.4 | Jun 5, 2026 |
| Click to Chat <= 4.22 - Authenticated (Contributor+) Stored DOM-Based Cross-Site Scripting via data-no_number ParameterCross-site scripting (XSS) · CVE-2025-5336 | ≤ 4.22 | 4.23 | Medium 6.4 | Jun 13, 2025 |
| Click to Chat – HoliThemes <= 3.35 - Authenticated (Contributor+) Local File InclusionArbitrary file read or deletion · CVE-2024-3849 | ≤ 3.35 | 4.0 | High 8.8 | Apr 17, 2024 |
| Click to Chat <= 3.18 - Authenticated (Contributor+) Stored Cross-Site Scripting via ShortcodeCross-site scripting (XSS) · CVE-2022-4480 | ≤ 3.18 | 3.18.1 | Medium 6.4 | Dec 21, 2022 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Oct 13, 2026.
Most common weaknesses in Click to Chat
Cross-site scripting (XSS)
3 issues
An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.
Arbitrary file read or deletion
1 issue
An attacker can read or delete files on the server. Deleting a configuration file can take the site offline, and reading one can expose passwords.
Frequently asked questions
Is Click to Chat safe to use?
Click to Chat is a well-known plugin with 600,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (4.47) and turn on automatic updates.
How do I find which version of Click to Chat my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.