CVE-2024-5031

MemberPress <= 1.11.29 - Authenticated (Contributor+) Blind Server-Side Request Forgery via mepr-user-file Shortcode

2024-05-21 20:06
stealthcopter

Strategic Overview

Status
Patched in 1.11.30
Affected Plugin
Memberpress
Affected Version
<= 1.11.29
CVSS
8.5High
Weakness type
CWE-918 · Server-Side Request Forgery (SSRF)
CVE
CVE-2024-5031
View all Memberpress vulnerabilities

At a glance

CVE-2024-5031 is a high-severity Server-Side Request Forgery (SSRF) vulnerability in the Memberpress WordPress plugin, affecting versions <= 1.11.29. It carries a CVSS score of 8.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 1.11.30; sites on affected versions should update now. Disclosed May 2024, reported by stealthcopter.

Vulnerability Overview

The Memberpress plugin for WordPress is vulnerable to Blind Server-Side Request Forgery in all versions up to, and including, 1.11.29 via the 'mepr-user-file' shortcode. This makes it possible for authenticated attackers, with Contributor-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

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 interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-918: Server-Side Request Forgery (SSRF)

Memberpress <= 1.11.29 carries this weakness at mepr-user-file, and reaching it takes an account at Contributor level or above. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.

The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For Memberpress the fix is 1.11.30: builds <= 1.11.29 are affected, anything from 1.11.30 onward is not.

Remediation

Update to version 1.11.30, or a newer patched version

How does WordSec protect against this?

An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Memberpress 1.11.30 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