CVE-2026-92097

9.1Critical

Published 14 Oct 2026 · NVD status: Deferred · AI triage by gemini-3.8-flash

9.1Critical

Attack vector: Network
Complexity: Low
Privileges needed: None
User interaction: None
Impact: High impact on confidentiality, integrity
Weakness: CWE-94

Impact

Unauthenticated attackers can execute arbitrary WordPress shortcodes remotely by sending crafted HTTP requests to archive pages. This requires only direct network access to the target site.

Root cause

The plugin injects unsanitized URL path bytes from the request into greetings templates after wp_kses() has already run, then passes the output directly into do_shortcode().

Affected systems

Click to Chat for WhatsApp plugin for WordPress up to and including version 4.44

CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Fix & remediation

Upgrade Click to Chat for WhatsApp to a version newer than 4.44. If an update cannot be deployed immediately, deactivate the plugin or switch greeting styles away from greetings-1 and greetings-2.

shell

$ wp plugin update click-to-chat-for-whatsapp

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

Ad · In-content banner

NVD description

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.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-92097