CVE-2023-6326

Master Slider - Responsive Touch Slider <= 3.9.10 - Cross-Site Request Forgery via process_bulk_action

2024-03-01 00:00
Rafshanzani Suhada

Strategic Overview

Status
Patched in 3.10.0
Affected Version
<= 3.9.10
CVSS
5.4Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-6326
View all Master Slider – Responsive Touch Slider vulnerabilities

At a glance

CVE-2023-6326 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Master Slider WordPress plugin, affecting versions <= 3.9.10. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.10.0; sites on affected versions should update now. Disclosed March 2024, reported by Rafshanzani Suhada.

Vulnerability Overview

The Master Slider – Responsive Touch Slider plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.9.10. This is due to missing or incorrect nonce validation on the 'process_bulk_action' function. This makes it possible for unauthenticated attackers to duplicate or delete arbitrary sliders via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE-2023-50900 and CVE-2024-6490 may be a duplicate of this issue.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Master Slider <= 3.9.10 carries this weakness at process_bulk_action, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Master Slider the fix is 3.10.0: builds <= 3.9.10 are affected, anything from 3.10.0 onward is not.

Remediation

Update to version 3.10.0, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Master Slider: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Master Slider 3.10.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C