MemberpressWordPress extension · Caseproof

CVE-2024-43956

CRITICAL · 9.8 CVSS v3.1 Published 2024-11-01
Fix available
A fix is available. Upgrade to 1.11.35 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Missing Authorization vulnerability in Caseproof, LLC Memberpress allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Memberpress: from n/a through 1.11.34.

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 · moderate confidence

Missing authorization vulnerability in MemberPress allows attackers to access functionality not properly constrained by access control lists (ACLs). This broken access control vulnerability in the WordPress plugin permits unauthorized users to perform privileged actions without proper authentication or authorization checks.

MitigationUpdate MemberPress to version 1.11.35 or later. Review user access controls and audit administrative functionality for unauthorized access.

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

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
High
Availability
High

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

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
    Check the WordPress plugins directory at wp-content/plugins/ for the memberpress folder, or run 'wp plugin list --status=active --format=json' to list active plugins
    Affected if MemberPress plugin is present and active in the WordPress installation
  2. Identify installed MemberPress version
    Open the main plugin file (typically memberpress.php) in the memberpress plugin folder and locate the 'Version' header in the plugin comments, or check in WordPress admin under Plugins > Installed Plugins
    Affected if The version displayed is less than 1.11.35
  3. Compare version against vulnerability threshold
    Review the version number found in the previous step against the affected range: any version below 1.11.35 is vulnerable
    Affected if The installed version is any version lower than 1.11.35, as the missing authorization check exists in the plugin code itself and requires no specific configuration to be exploitable

A user is affected if the installed MemberPress version is below 1.11.35, as the broken access control vulnerability exists in the plugin code itself regardless of configuration settings.

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.35 or later
Fixed in 1.11.35
Interim mitigation

Update MemberPress to version 1.11.35 or later. Review user access controls and audit administrative functionality for unauthorized access.

Recommended fix High confidence

MemberPress 1.11.35

  1. Backup your WordPress database and files before performing any updates
  2. Log in to your WordPress admin dashboard
  3. Navigate to Dashboard > Updates or go to Plugins > Installed Plugins
  4. Locate MemberPress in the plugin list
  5. If version 1.11.35 or higher is available, click Update Now to install the patched version
  6. Alternatively, download MemberPress 1.11.35 or later from the official source and upload via Plugins > Add New > Upload Plugin
  7. After updating, verify the version number in Plugins > Installed Plugins confirms 1.11.35 or higher is active
  8. Test critical functionality including member registration, subscription access, and payment processing to confirm the update was successful

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

Fix this in Memberpress Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-43956 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