CVE-2026-4088
Stored XSS in Switch CTA Box WordPress Plugin Allows Script Injection
Publication date: 2026-04-22
Last updated on: 2026-04-22
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordfence | switch_cta_box | to 1.1 (inc) |
| wpplugin | switch_cta_box | to 1.1 (inc) |
| wp_plugin | switch_cta_box | to 1.1 (inc) |
| wordpressthemes | the_switch_cta_box | to 1.1 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The Switch CTA Box plugin for WordPress has a Stored Cross-Site Scripting (XSS) vulnerability in its 'wppw_cta_box' shortcode in all versions up to and including 1.1.
This vulnerability arises because the plugin does not properly sanitize or escape user-supplied post meta values such as 'cta_box_button_link', 'cta_box_button_id', 'cta_box_button_text', and 'cta_box_description'.
As a result, authenticated users with contributor-level access or higher can inject malicious scripts into pages, which then execute whenever any user views those pages.
How can this vulnerability impact me? :
This vulnerability can allow attackers with contributor-level access to inject arbitrary web scripts into pages.
These scripts execute in the browsers of users who visit the affected pages, potentially leading to theft of user data, session hijacking, or other malicious actions.
Because the attack requires authenticated access, it may be used to escalate privileges or compromise site integrity from within.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows authenticated attackers with contributor-level access and above to inject arbitrary web scripts via stored cross-site scripting (XSS). This can lead to unauthorized access to user data or session hijacking, which may compromise the confidentiality and integrity of personal data.
Such security weaknesses can impact compliance with standards and regulations like GDPR and HIPAA, which require protection of personal data against unauthorized access and ensuring data integrity.
However, the provided context does not explicitly discuss the direct impact on compliance with these regulations.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves stored Cross-Site Scripting (XSS) via the 'wppw_cta_box' shortcode in the Switch CTA Box WordPress plugin. Detection involves checking for the presence of this plugin and inspecting post meta values related to 'cta_box_button_link', 'cta_box_button_id', 'cta_box_button_text', and 'cta_box_description' for malicious scripts.
You can detect the vulnerability by searching your WordPress database for suspicious script tags or JavaScript code in these post meta fields. For example, using SQL commands to query the wp_postmeta table:
- SELECT * FROM wp_postmeta WHERE meta_key IN ('cta_box_button_link', 'cta_box_button_id', 'cta_box_button_text', 'cta_box_description') AND meta_value LIKE '%<script>%';
Additionally, you can check if the plugin 'switch_cta_box' is installed and its version is 1.1 or below, as all these versions are vulnerable.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, immediately update the Switch CTA Box plugin to a version that fixes the issue if available.
If no update is available, restrict contributor-level and higher users from adding or editing the affected shortcode or post meta fields until a patch is applied.
As a temporary workaround, sanitize and escape all user-supplied input related to the shortcode fields ('cta_box_button_link', 'cta_box_button_id', 'cta_box_button_text', and 'cta_box_description') before outputting them in HTML.
Also, consider scanning your site for injected scripts and removing any malicious content found in the affected post meta fields.