CVE-2024-31430

BEAR <= 1.1.4.1 & WOLF <= 1.0.8.1 - Cross-Site Request Forgery to Notice Dismissal

2024-04-10 00:00
Dhabaleshwar Das

Strategic Overview

Status
Patched in 1.0.8.2
Affected Plugin
WOLF – WordPress Posts Bulk Editor and Manager Professional
Affected Version
<= 1.0.8.1
CVSS
5.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-31430
View all WOLF – WordPress Posts Bulk Editor and Manager Professional vulnerabilities

At a glance

CVE-2024-31430 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WOLF WordPress plugin, affecting versions <= 1.0.8.1. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.0.8.2; sites on affected versions should update now. Disclosed April 2024, reported by Dhabaleshwar Das.

Vulnerability Overview

Multiple plugins and/or themes for WordPress are vulnerable to Cross-Site Request Forgery in various versions. This is due to missing or incorrect nonce validation on the admin_init() hook. This makes it possible for unauthenticated attackers to dismiss notices 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, and no interaction from a victim user.

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

WOLF <= 1.0.8.1 carries this weakness at admin_init(), 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 WOLF the fix is 1.0.8.2: builds <= 1.0.8.1 are affected, anything from 1.0.8.2 onward is not.

Remediation

Update to version 1.0.8.2, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-31430https://www.wordfence.com/threat-intel/vulnerabilities/id/12188a74-b1a6-4aa4-88b4-2d0d0dd32916https://nvd.nist.gov/vuln/detail/CVE-2024-31430

Related records

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