dbcve.org
MemberpressWordPress extension · Caseproof

CVE-2024-11299

HIGH · 7.5 CVSS v3.1 Published 2025-04-22
Fix available
A fix is available. Upgrade to after 1.11.37 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 Sensitive Information Exposure in all versions up to, and including, 1.11.37 via the WordPress core search feature. This makes it possible for unauthenticated attackers to extract sensitive data from posts that have been restricted to higher-level roles such as administrator.

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 is vulnerable to sensitive information exposure via the WordPress core search feature. In affected versions up to 1.11.37, posts restricted to higher-level roles (such as administrator) can be returned in search results, allowing unauthenticated attackers to extract sensitive data from these protected posts.

MitigationUpdate MemberPress to version 1.11.38 or later to patch this vulnerability. Review previously restricted content to determine if sensitive data may have been exposed prior to patching.

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.37

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Verify MemberPress plugin installation and version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Locate 'MemberPress' and note the version number displayed. Alternatively, check the plugin file header in /wp-content/plugins/memberpress/memberpress.php
    Affected if The installed version is 1.11.37 or lower
  2. Confirm unauthenticated search access
    Open a browser in incognito/private mode. Use the WordPress search function at yoursite.com/?s= to perform a search query without logging in.
    Affected if Search results are returned to unauthenticated users (not redirected to login)
  3. Identify role-restricted content
    In WordPress admin, go to MemberPress > Rules. Review any rules that restrict access based on WordPress user roles (such as Administrator, Editor, or custom roles).
    Affected if There are active MemberPress rules that restrict content to specific roles above Subscriber
  4. Test search exposure of restricted content
    Perform a search using terms that might match restricted content titles or content (e.g., common words from admin-only posts). Compare search results against what an unauthenticated user sees.
    Affected if Posts protected by role-based MemberPress rules appear in search results visible to unauthenticated users

If MemberPress version is 1.11.37 or below AND your site allows unauthenticated search AND you have role-based content restrictions configured, your restricted content may have been exposed via search results.

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 a release after 1.11.37
Interim mitigation

Update MemberPress to version 1.11.38 or later to patch this vulnerability. Review previously restricted content to determine if sensitive data may have been exposed prior to patching.

Recommended fix Moderate confidence

Memberpress version > 1.11.37 (latest stable release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find Memberpress in the plugin list
  4. Click 'Update Now' if an update is available, or manually download the latest version from memberpress.com and upload it
  5. Verify the update was successful by checking the plugin version is above 1.11.37

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
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-11299 — 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-11299 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