dbcve.org
MemberpressWordPress extension · Caseproof

CVE-2024-5031

MEDIUM · 6.4 CVSS v3.1 Published 2024-05-22
Fix available
A fix is available. Upgrade to 1.11.30 or later.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The MemberPress WordPress plugin contains a blind Server-Side Request Forgery (SSRF) vulnerability in the 'mepr-user-file' shortcode affecting all versions up to 1.11.29. Authenticated attackers with Contributor-level access can cause the server to make arbitrary HTTP requests to internal or external resources, potentially accessing sensitive internal services.

MitigationUpgrade MemberPress to version 1.11.30 or later. If immediate upgrade is not possible, restrict or disable Contributor-level user capabilities and the mepr-user-file shortcode as a temporary workaround.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MemberpressWordPress extension
Affected:< 1.11.30

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm MemberPress plugin is installed
    Navigate to WordPress Admin > Plugins and look for 'MemberPress' or 'MemberPress' by Caseproof in the installed plugins list
    Affected if MemberPress plugin is present in the WordPress installation
  2. Check installed MemberPress version
    In WordPress Admin > Plugins, click on the MemberPress plugin to view its version details, or check the plugin file header in wp-content/plugins/memberpress/memberpress.php
    Affected if Version is below 1.11.30 (e.g., 1.11.29 or earlier)
  3. Verify mepr-user-file shortcode is available
    Check if the shortcode is callable by viewing page source or using a WordPress shortcode checker; the shortcode is [mepr-user-file] and may be used in posts, pages, or theme files
    Affected if The mepr-user-file shortcode exists and is accessible within the WordPress site
  4. Identify users with Contributor-level access
    In WordPress Admin > Users, review user roles and check for any accounts assigned the Contributor role
    Affected if At least one user account has Contributor-level permissions or higher (Contributor, Author, Editor, Administrator)
  5. Confirm shortcode processing is active
    Test if the shortcode renders by creating a test page with [mepr-user-file] and accessing it, or check memberpress-shortcodes.php for active shortcode registration
    Affected if The mepr-user-file shortcode processes requests on the site

You are affected if MemberPress version is below 1.11.30 AND the mepr-user-file shortcode is accessible to users with Contributor-level access or higher.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.11.30 or later
Fixed in 1.11.30
Interim mitigation

Upgrade MemberPress to version 1.11.30 or later. If immediate upgrade is not possible, restrict or disable Contributor-level user capabilities and the mepr-user-file shortcode as a temporary workaround.

Recommended fix High confidence

Memberpress 1.11.30

  1. 1. Create a complete backup of the WordPress site including database and files
  2. 2. Navigate to Dashboard > Plugins in the WordPress admin panel
  3. 3. Locate the MemberPress plugin in the installed plugins list
  4. 4. Click the 'Update now' link if an update is available, or manually upload version 1.11.30 or higher from the WordPress repository
  5. 5. Verify the plugin version after update by checking the Plugins page
  6. 6. Test the 'mepr-user-file' shortcode functionality to ensure normal operations work
  7. 7. Confirm the update by reviewing the MemberPress Changelog for version 1.11.30
Caveat Review the Memberpress changelog for version 1.11.30 to confirm no breaking changes for your specific configuration; standard WordPress plugin update practices apply

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Memberpress Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-5031 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-5031 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data