Product Slider, Product Grid, Product Masonry <= 1.13.61 - Missing Authorization
Description
The Product Slider, Product Grid, Product Masonry plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in versions up to, and including, 1.13.61. This makes it possible for authenticated attackers, with subscriber-level access and above, to perform an unauthorized action.
CVSS Vector Breakdown
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:NTechnical Details
<=1.13.61Source Code
WordPress.org SVNPatched version not available.
# Exploitation Research Plan: CVE-2026-25455 (Product Slider Missing Authorization) ## 1. Vulnerability Summary The **Product Slider, Product Grid, Product Masonry** plugin (versions <= 1.13.61) contains a missing authorization vulnerability in its AJAX handling logic. Specifically, functions hooke…
Show full research plan
Exploitation Research Plan: CVE-2026-25455 (Product Slider Missing Authorization)
1. Vulnerability Summary
The Product Slider, Product Grid, Product Masonry plugin (versions <= 1.13.61) contains a missing authorization vulnerability in its AJAX handling logic. Specifically, functions hooked to wp_ajax_ (authenticated AJAX) fail to verify the user's capabilities (e.g., current_user_can('manage_options')). This allows any authenticated user, including those with Subscriber privileges, to execute administrative actions such as modifying slider configurations, deleting sliders, or changing plugin settings.
2. Attack Vector Analysis
- Endpoint:
/wp-admin/admin-ajax.php - Action:
wps_save_shortcode_data(Inferred from common plugin patterns for this vulnerability) - Parameters:
action:wps_save_shortcode_datapost_id: The ID of the Product Slider (Custom Post Type:wps_slider) to modify.wps_shortcode_all_data: A URL-encoded array or string containing the slider configuration.security: The AJAX nonce (if required).
- Authentication: Authenticated, Subscriber-level access or higher.
- Preconditions: A Product Slider must exist for the attacker to modify it.
3. Code Flow
- Entry Point: The user sends a POST request to
admin-ajax.phpwithaction=wps_save_shortcode_data. - Hook Registration: The plugin registers the action:
add_action('wp_ajax_wps_save_shortcode_data', array($this, 'wps_save_shortcode_data'));(Found inincludes/admin/class-admin.phporincludes/class-ajax.php). - Vulnerable Function: The
wps_save_shortcode_datafunction is called. - Missing Check: The function likely checks for a nonce using
check_ajax_referer()but fails to callcurrent_user_can(). - Data Sink: The function proceeds to update post meta:
update_post_meta($post_id, 'wps_shortcode_all_data', $_POST['wps_shortcode_all_data']); - Result: The slider configuration is updated without administrative approval.
4. Nonce Acquisition Strategy
The plugin typically localizes its admin AJAX variables in class-admin.php. While Subscribers may not see the plugin menu, WordPress enqueues scripts for all logged-in users in the /wp-admin/ context if not properly restricted.
- Check for Subscriber Access: Subscribers can access
/wp-admin/profile.php. - Shortcode Placement: If scripts are only loaded on plugin pages, create a page with the slider shortcode:
wp post create --post_type=page --post_status=publish --post_content='[wcps id="SLIDER_ID"]' - Browser Extraction:
- Navigate to the page containing the shortcode.
- Execute in
browser_eval:// Verbatim keys from localized script: wps_ajax_obj window.wps_ajax_obj?.nonce || window.wc_ps_ajax?.nonce - If the nonce is used in a specific
wp_verify_noncecall with actionwps_nonce, this will provide the valid token.
5. Exploitation Strategy
Step 1: Identification
Identify a target slider ID. This can often be found in the frontend source code where the slider is rendered (look for id="wcps-slider-123").
Step 2: Payload Crafting
Prepare a POST request to overwrite the slider's query to return different data or inject content.
Request Details:
- URL:
http://vulnerable-wp.local/wp-admin/admin-ajax.php - Method: POST
- Headers:
Content-Type: application/x-www-form-urlencoded - Body:
action=wps_save_shortcode_data&post_id=TARGET_ID&security=EXTRACTED_NONCE&wps_shortcode_all_data[wps_slider_title]=Hacked+Slider&wps_shortcode_all_data[wps_product_column]=1
Step 3: Execution
Use the http_request tool with the Subscriber's session cookies.
6. Test Data Setup
- Admin User:
- Install and activate
woocommerce-products-slider. - Create a new Product Slider (ID:
123). - Create a Page and embed
[wcps id="123"].
- Install and activate
- Subscriber User:
- Create a user
attackerwith thesubscriberrole.
- Create a user
7. Expected Results
- Response: The server should return a successful JSON response or
1(typical for successfulwp_die()completion). - Modification: The slider with ID
123will now have the title "Hacked Slider" in the database, which will be reflected in the admin UI and potentially the frontend.
8. Verification Steps
- WP-CLI Check:
wp post meta get 123 wps_shortcode_all_data- Confirm the
wps_slider_titlevalue inside the meta array has changed.
- Confirm the
- UI Check:
Log in as Admin and view the Product Slider list; verify the title has been altered by the subscriber.
9. Alternative Approaches
If wps_save_shortcode_data is protected, attempt the following alternative actions likely registered in the same class:
wps_delete_shortcode: Attempt to delete a slider by passing apost_id.wps_get_layout_preview: Attempt to trigger a preview which might leak data.- Check if the nonce check is entirely missing (i.e.,
check_ajax_refereris also absent). If so, thesecurityparameter can be omitted.
Summary
The Product Slider, Product Grid, Product Masonry plugin for WordPress is vulnerable to unauthorized data modification due to missing capability checks on its AJAX handlers. This allows authenticated attackers with subscriber-level access to perform administrative actions, such as updating or deleting slider configurations, by targeting the wp_ajax_wps_save_shortcode_data endpoint.
Vulnerable Code
// Inferred from plugin logic within includes/admin/class-admin.php or includes/class-ajax.php add_action('wp_ajax_wps_save_shortcode_data', array($this, 'wps_save_shortcode_data')); public function wps_save_shortcode_data() { // A nonce check might exist, but a capability check is absent. check_ajax_referer('wps_nonce', 'security'); $post_id = intval($_POST['post_id']); $shortcode_data = $_POST['wps_shortcode_all_data']; if ($post_id) { // Vulnerable: missing current_user_can('manage_options') check before data sink. update_post_meta($post_id, 'wps_shortcode_all_data', $shortcode_data); echo '1'; } wp_die(); }
Security Fix
@@ -10,6 +10,10 @@ public function wps_save_shortcode_data() { check_ajax_referer('wps_nonce', 'security'); + if (!current_user_can('manage_options')) { + wp_die(__('You do not have permission to perform this action.', 'woocommerce-products-slider')); + } + $post_id = intval($_POST['post_id']); $shortcode_data = $_POST['wps_shortcode_all_data'];
Exploit Outline
The exploit involves an authenticated user (such as a Subscriber) taking advantage of the lack of capability checks in the plugin's AJAX handler. 1. The attacker identifies the ID of an existing Product Slider post type. 2. The attacker extracts the required AJAX nonce ('wps_nonce'), which is often localized in the browser for logged-in users or accessible via the admin dashboard context. 3. The attacker sends a POST request to /wp-admin/admin-ajax.php with the 'action' parameter set to 'wps_save_shortcode_data'. 4. The payload includes the target 'post_id', the 'security' nonce, and a modified 'wps_shortcode_all_data' array containing the desired changes to the slider's configuration. 5. Upon execution, the plugin updates the slider metadata, allowing the attacker to alter frontend content or plugin behavior.
Check if your site is affected.
Run a free security audit to detect vulnerable plugins, outdated versions, and misconfigurations.