CVE-2024-32958

Slash Admin <= 3.8.1 - Cross-Site Request Forgery

2024-04-23 00:00
Cronus

Strategic Overview

Status
Patched in 3.8.2
Affected Plugin
Slash Admin
Affected Version
<= 3.8.1
CVSS
6.1Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-32958
View all Slash Admin vulnerabilities

At a glance

CVE-2024-32958 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Slash Admin WordPress plugin, affecting versions <= 3.8.1. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.8.2; sites on affected versions should update now. Disclosed April 2024, reported by Cronus.

Vulnerability Overview

The Slash Admin plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.8.1. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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)

Reaching this weakness in Slash Admin <= 3.8.1 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 Slash Admin the fix is 3.8.2: builds <= 3.8.1 are affected, anything from 3.8.2 onward is not.

Remediation

Update to version 3.8.2, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

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