CVE-2025-13838
Unknown Unknown - Not Provided
Stored XSS in WishSuite WordPress Plugin Allows Script Injection

Publication date: 2025-12-21

Last updated on: 2025-12-21

Assigner: Wordfence

Description
The WishSuite plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'button_text' parameter of the 'wishsuite_button' shortcode in all versions up to, and including, 1.5.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-21
Last Modified
2025-12-21
Generated
2026-05-07
AI Q&A
2025-12-21
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
wordpress wishsuite *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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?

CVE-2025-13838 is a Stored Cross-Site Scripting (XSS) vulnerability in the WishSuite WordPress plugin affecting versions up to and including 1.5.1. It occurs via the 'button_text' parameter of the 'wishsuite_button' shortcode due to insufficient input sanitization and output escaping. This allows authenticated users with Contributor-level access or higher to inject arbitrary web scripts into pages. These scripts execute whenever any user accesses the injected page, potentially compromising site security. [4]


How can this vulnerability impact me? :

This vulnerability can allow attackers with Contributor-level access or above to inject malicious scripts into website pages via the 'button_text' shortcode parameter. When other users visit these pages, the injected scripts execute in their browsers, potentially leading to theft of user credentials, session hijacking, defacement, or other malicious actions. This compromises the security and integrity of the affected website and its users. [4]


What immediate steps should I take to mitigate this vulnerability?

To mitigate the vulnerability CVE-2025-13838 in the WishSuite WordPress plugin, immediately update the plugin to version 1.5.2 or later. This update includes sanitization of the 'button_text', 'button_added_text', and 'button_exist_text' shortcode attributes using the wp_kses function with a custom whitelist of allowed HTML tags and attributes, effectively preventing stored Cross-Site Scripting (XSS) attacks. Ensuring your plugin is updated to 1.5.2 will apply these security fixes and maintain compatibility with WooCommerce 10.3.6. [4]


How can this vulnerability be detected on my network or system? Can you suggest some commands?

To detect this vulnerability on your system, you should check if your WordPress installation is running the WishSuite plugin version 1.5.1 or earlier, as these versions are vulnerable. You can do this by inspecting the plugin version via the WordPress admin dashboard or by checking the plugin files directly. Additionally, you can search for the presence of the 'wishsuite_button' shortcode with potentially malicious 'button_text' parameters in your posts or pages. Since this is a Stored Cross-Site Scripting (XSS) vulnerability, monitoring HTTP requests and responses for injected scripts in pages containing the shortcode can help detect exploitation attempts. There are no specific commands provided in the resources, but general approaches include: 1. Using WP-CLI to check plugin version: `wp plugin list --status=active` and verify WishSuite version. 2. Searching the WordPress database for suspicious shortcode usage, e.g., via SQL: `SELECT post_content FROM wp_posts WHERE post_content LIKE '%[wishsuite_button%';` 3. Using web vulnerability scanners or proxy tools (like Burp Suite) to detect XSS payloads in pages using the shortcode. 4. Reviewing web server logs for unusual requests or payloads targeting the 'button_text' parameter. Since no explicit commands are provided in the resources, these general methods are recommended. [4]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart