CVE-2024-31301

Multiple Page Generator Plugin – MPG <= 3.4.0 - Cross-Site Request Forgery

2024-04-05 00:00
Majed Refaea

Strategic Overview

Status
Patched in 3.4.1
Affected Plugin
MPG – Multiple Page Generator, Bulk Landing Pages & Programmatic SEO
Affected Version
<= 3.4.0
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-31301
View all MPG – Multiple Page Generator, Bulk Landing Pages & Programmatic SEO vulnerabilities

At a glance

CVE-2024-31301 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the MPG WordPress plugin, affecting versions <= 3.4.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.4.1; sites on affected versions should update now. Disclosed April 2024, reported by Majed Refaea.

Vulnerability Overview

The Multiple Page Generator Plugin – MPG plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.4.0. This is due to missing or incorrect nonce validation on the delete_project action. This makes it possible for unauthenticated attackers to delete projects 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 MPG <= 3.4.0 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 MPG the fix is 3.4.1: builds <= 3.4.0 are affected, anything from 3.4.1 onward is not.

Remediation

Update to version 3.4.1, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-31301https://www.wordfence.com/threat-intel/vulnerabilities/id/aa15df6a-3411-4d69-8337-a3944ceae9eehttps://nvd.nist.gov/vuln/detail/CVE-2024-31301

Related records

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