CVE-2025-15488
Arbitrary Shortcode Execution in Responsive Plus WordPress Plugin
Publication date: 2026-03-26
Last updated on: 2026-03-26
Assigner: WPScan
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| responsive_plus | responsive_plus | to 3.4.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-15488 is a vulnerability in the Responsive Plus WordPress plugin versions before 3.4.3 that allows unauthenticated users to execute arbitrary shortcodes. This happens because the plugin's AJAX action named update_responsive_woo_free_shipping_left_shortcode processes the content_rech_data parameter as a shortcode without properly validating the user's authorization.
An attacker can exploit this by sending a crafted POST request with malicious shortcode content, which the plugin then executes, potentially injecting unauthorized content or triggering other malicious shortcode behaviors.
How can this vulnerability impact me? :
This vulnerability can allow unauthenticated attackers to inject arbitrary shortcode content into your WordPress site using the Responsive Plus plugin. This can lead to unauthorized content injection, which may affect the integrity and appearance of your website.
Depending on the shortcode executed, it could also lead to further malicious actions such as executing unintended code or exposing sensitive information, thereby compromising the security of your site.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for unauthorized AJAX POST requests to the endpoint `/wp-admin/admin-ajax.php` with the parameter `action=update_responsive_woo_free_shipping_left_shortcode`.
One way to detect exploitation attempts is to look for POST requests containing the `content_rech_data` parameter with suspicious shortcode content.
Suggested commands to detect this on a system with access to web server logs or via command line tools include:
- Using grep to search web server logs for the vulnerable AJAX action: `grep 'action=update_responsive_woo_free_shipping_left_shortcode' /path/to/access.log`
- Using curl to test if the endpoint is vulnerable (requires capturing a valid cookie from a WooCommerce session): `curl -X POST -b 'cookie=YOUR_COOKIE_HERE' -d 'action=update_responsive_woo_free_shipping_left_shortcode&content_rech_data=[caption]TEST[/caption]' https://yourwordpresssite.com/wp-admin/admin-ajax.php`
Additionally, intercepting and analyzing HTTP traffic with tools like Burp Suite can help identify if the vulnerable AJAX action is being called with unvalidated shortcode content.
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the Responsive Plus WordPress plugin to version 3.4.3 or later, where the vulnerability is fixed by proper authorization validation.
Until the update can be applied, you can temporarily disable or restrict access to the vulnerable AJAX action `update_responsive_woo_free_shipping_left_shortcode` to prevent unauthenticated users from exploiting it.
Additional mitigation steps include monitoring web server logs for suspicious requests to the vulnerable AJAX endpoint and implementing Web Application Firewall (WAF) rules to block unauthorized POST requests targeting this action.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthenticated attackers to execute arbitrary shortcodes due to improper authorization validation. This can lead to unauthorized content injection or other malicious behaviors within the WordPress site.
Such unauthorized access and potential data manipulation could impact compliance with common standards and regulations like GDPR and HIPAA, which require strict access controls and protection of data integrity.
However, the provided information does not explicitly describe the direct effects on compliance with these standards.