CVE-2026-92097

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

2026-10-13 12:25
Kuba

Strategic Overview

Status
Patched in 4.45
Affected Plugin
Click to Chat – HoliThemes
Affected Version
<= 4.44
CVSS
9.1Critical
Weakness type
CWE-94 · Improper Control of Generation of Code ('Code Injection')
CVE
CVE-2026-92097
View all Click to Chat – HoliThemes vulnerabilities

At a glance

CVE-2026-92097 is a critical-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the Click to Chat WordPress plugin, affecting versions <= 4.44. It carries a CVSS score of 9.1 (reachable over the network; low attack complexity; high confidentiality, integrity impact). Exploitation requires no authentication. The issue is fixed in version 4.45; sites on affected versions should update now. Disclosed October 2026, reported by Kuba.

Vulnerability Overview

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.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity.

CWE-94: Improper Control of Generation of Code ('Code Injection')

Click to Chat <= 4.44 carries this weakness at REQUEST_URI, and reaching it takes no account at all. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.

The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For Click to Chat the fix is 4.45: builds <= 4.44 are affected, anything from 4.45 onward is not.

Remediation

Update to version 4.45, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Click to Chat 4.45 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

https://www.cve.org/CVERecord?id=CVE-2026-92097https://www.wordfence.com/threat-intel/vulnerabilities/id/cf625e34-1f51-42a3-8daa-a5188dea226ehttps://nvd.nist.gov/vuln/detail/CVE-2026-92097

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C