Paid Memberships ProWordPress extension · Strangerstudios
CVE-2024-32794
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Paid Memberships Pro.This issue affects Paid Memberships Pro: from n/a through 2.12.10.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Paid Memberships Pro WordPress plugin allows attackers to trick authenticated users into performing unintended administrative actions (such as modifying membership settings or user permissions) by forging requests. The vulnerability affects all versions through 2.12.10 and stems from missing or improper anti-CSRF token validation on sensitive plugin actions.
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
Paid Memberships ProWordPress extension
< 3.0CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Paid Memberships Pro is installedLog in to WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Paid Memberships Pro' in the list. Alternatively, check the file system at wp-content/plugins/ for a folder named 'paid-memberships-pro'.Affected if The plugin folder exists and the plugin is active on the WordPress site.
-
Determine the installed plugin versionIn WordPress admin, find Paid Memberships Pro in the plugins list and read the version number displayed beneath the plugin name. Alternatively, open the main plugin file (paid-memberships-pro.php) in wp-content/plugins/paid-memberships-pro/ and locate the version header comment at the top of the file.Affected if The version number is less than 3.0 (or less than 2.12.11 if using the intermediate patch).
-
Verify the plugin is processing authenticated user requestsCheck if the plugin is active and configured to handle membership operations. Navigate to Memberships > Settings in the WordPress admin to confirm the plugin is operational. Inspect network requests when saving membership settings to see if the server processes the authenticated session.Affected if The plugin is active and accepts requests from authenticated users (any logged-in WordPress user with membership-related capabilities).
-
Confirm sensitive admin actions are accessibleAttempt to access or observe the plugin's admin pages that handle membership settings, user role modifications, or permission changes (such as Memberships > Members List, Memberships > Settings > Payment Settings). Check if these actions process form submissions or URL parameters without requiring explicit CSRF token verification.Affected if The plugin's administrative functions for modifying membership settings or user permissions are accessible and operational without visible CSRF token validation.
The environment is affected if Paid Memberships Pro is installed with a version prior to 3.0 (or 2.12.11) and the plugin's administrative functions handling membership settings or user permissions are accessible to authenticated users.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.0
Update Paid Memberships Pro to version 2.12.11 or later which contains the patched fix. If immediate update is not possible, disable the plugin's administrative functions or implement additional CSRF tokens at the web server level as a temporary measure.
Paid Memberships Pro 3.0 or later
- 1. Back up your WordPress database and files before updating.
- 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
- 3. Find Paid Memberships Pro in the plugin list.
- 4. If an update is available, click 'Update Now' to upgrade to version 3.0 or later.
- 5. Alternatively, download Paid Memberships Pro 3.0+ from the official WordPress plugin repository or your account at paidmembershipspro.com
- 6. Upload the new version via Plugins > Add New > Upload Plugin if automatic update doesn't work.
- 7. After updating, test critical membership flows (registration, login, subscription management) to ensure functionality.
- 8. Verify the plugin version shows 3.0 or higher in Plugins > Installed Plugins.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Paid Memberships Pro
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-32794 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-32794 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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