VulnCrest
Search
Create account
Report an incident
Radar sectionsDatabase
Check my site
WordPress plugin

Click to Chat <= 4.44 — Unauthenticated Arbitrary Shortcode Execution via REQUEST_URI via {url} Placeholder

CVE-2026-92097Published · Updated

Action summary

Affected: ≤4.44Update to 4.45 or newer

All remediation steps
Watch plugin
Severity
Critical9.1
CVSS
9.1
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:H Confidentiality
High
I:H Integrity
High
A:N Availability
None
Weakness
CWE-94 Improper Control of Generation of Code
Required access
No account needed
Exploit prediction (EPSS)
0.5% chance in 30 days45th percentile
CISA KEV
Not listed
On this page8

Am I affected?

Click to Chat – HoliThemes click-to-chat-for-whatsapp

  1. Affected≤ 4.44
  2. Patched in4.45

Update to 4.45 or newer.

You are affected if you run ≤ 4.44. Version 4.45 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Click to Chat – HoliThemes.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 4.45, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Click to Chat – HoliThemes to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Kuba.

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 placeholder from a sanitize_text_field()-filtered $_SERVER['REQUEST_URI'] on archive pages and then passing the substituted greeting content to do_shortcode() in the greetings-1 and greetings-2 templates, without stripping shortcode delimiters. Because wp_kses() runs against main_content BEFORE the {url} substitution, the attacker-controlled URL bytes reach do_shortcode() unfiltered. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes registered by WordPress core, the active theme, or any other plugin (e.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Click to Chat – HoliThemes

All 5
More vulnerabilities in Click to Chat – HoliThemes
SeverityVulnerabilityCVEPublished
Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting via 'num' Shortcode Parameter
≤4.39Update to 4.40
CVE-2026-7795
Medium6.4Authenticated (Contributor+) Stored DOM-Based Cross-Site Scripting via data-no_number Parameter
≤4.22Update to 4.23
CVE-2025-5336
High8.8Authenticated (Contributor+) Local File Inclusion
≤3.35Update to 4.0
CVE-2024-3849
Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode
≤3.18Update to 3.18.1
CVE-2022-4480

Timeline

  1. CVE published

    Severity critical, CVSS 9.1

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
EPSS
Exploit Prediction Scoring System by FIRST.org.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Jump to

Are you sure?