Plugin security / Click to Chat
Click to Chat vulnerability: is your WooCommerce store affected?
Click to Chat has 2 serious security holes rated 7 or higher out of 10 that someone can use with no login or with only a customer account. The newest was published on 5 June 2026. Every one is fixed: update to 4.45 or newer.
Short answer: your store is affected if it runs Click to Chat older than 4.45. Update to 4.45 or newer, on a copy of the store first if you can.
In our check of 3,600 live UK and US WooCommerce stores (31 October 2026 to 1 November 2026), 27 were running a version of Click to Chat with a serious hole that already had a fix. How we checked.
The security holes
Newest first. Each one is published in a public security database and fixed in the version shown.
Missing permission check
An action that should need permission could be done without it.
Score 9.1 (critical)no login neededAffected: older than 4.45Fixed in 4.45Published 5 June 2026CVE-2026-92097
Advisory: The Click to Chat for WhatsApp plugin for WordPress is vulnerable to Arbitrary Shortcode Execution in versions up to, and including, 4.44 This is due to the greetings_dialog() function building the {url} template...
File inclusion
Someone could make the plugin load files it shouldn't, which can expose data or run code.
Score 8.8 (high)needs only a customer accountAffected: older than 4.0Fixed in 4.0Published 17 April 2024CVE-2024-3849
Advisory: The Click to Chat – HoliThemes plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 3.35.
How to check your version
- Log in to WordPress and open
Plugins > Installed Plugins. - Find Click to Chat. The version number is under its name. If it is lower than 4.45, your store is affected.
- No login to hand? Open
https://yourstore.com/wp-content/plugins/click-to-chat-for-whatsapp/readme.txtin a browser, with your own address in place of yourstore.com, and read theStable tagline. Some hosts block this file; then use step 1.
How to fix it
- Make a backup, or better, a staging copy of the store (most hosts have a one-click staging button).
- On the copy, update Click to Chat to 4.45 or newer:
Dashboard > Updates, orUpdate nowon the Plugins page. - If no update shows, it may be a paid version whose licence has run out: download the new version from the seller's site and upload it.
- Place a test order on the copy: add to cart, check out, pay with a test method. Check the pages that use Click to Chat.
- If everything works, make the same update on the live store and place one more test order.
- If you no longer use Click to Chat, delete it instead of leaving it deactivated.
Not sure, or no time?
Get a free check of your store: we look at its public pages for plugins with known holes, and reply within one working day. Or we fix it for you: we update your store on a copy, place a test order, and only then change the live store, for a fixed £99 / $119.
Free store check Fix it for me on a copyQuestions
- Which Click to Chat version fixes it?
- Version 4.45 or newer fixes all 2 issues on this page.
- How do I know if my store is affected?
- Your store is affected if it runs Click to Chat older than 4.45. In WordPress, open Plugins and read the version under Click to Chat. Without logging in, open yourstore.com/wp-content/plugins/click-to-chat-for-whatsapp/readme.txt and read the Stable tag line.
- I don't use Click to Chat any more. Is a deactivated copy safe?
- Deactivating it lowers the risk but leaves the old code on your server. If you don't use it, delete it; if you do, update it.
- Can someone fix it for me?
- Yes. We update the store on a copy first, place a test order, and only then make the same change on the live store, for a fixed price.
Vulnerability data: WPVulnerability (wpvulnerability.net, CC0), which links each entry to its CVE or advisory. Store numbers: Tadrik's own checks of public pages, aggregates only. Page updated 3 November 2026.