CVE-2026-57659
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 · uneditedUnauthenticated Cross Site Request Forgery (CSRF) in Paid Memberships Pro - Add Member From Admin <= 0.7.2 versions.
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 confidenceAn unauthenticated Cross Site Request Forgery (CSRF) vulnerability in the 'Add Member From Admin' functionality of the Paid Memberships Pro WordPress plugin (versions <= 0.7.2) allows remote attackers to trick authenticated administrators into adding malicious user accounts to the membership site without the admin's consent.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- 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.
-
Confirm Paid Memberships Pro is installedNavigate to WordPress admin dashboard, go to Plugins section, and locate 'Paid Memberships Pro' in the list of installed pluginsAffected if The plugin is not installed in the WordPress environment
-
Identify the installed version numberIn the Plugins list, click on 'Plugin Details' for Paid Memberships Pro, or check the plugin's main PHP file (pmpro-member.php or similar) for the 'Version:' header commentAffected if The displayed version is 0.7.2 or any version below 0.7.2
-
Verify the Add Member functionality existsIn WordPress admin, navigate to the Memberships > Members section or equivalent PMPro admin menu, and locate the 'Add Member' or 'Add Member From Admin' optionAffected if The Add Member functionality is present and accessible to administrators
-
Check for anti-CSRF token implementation in the Add Member formAccess the Add Member form via admin, view the page source (right-click > View Page Source), and search for a nonce field (wpnonce, _wpnonce, or similar) and verify it is submitted with the formAffected if The Add Member form lacks a CSRF protection nonce token or the submitted form does not validate a nonce on the server side
The environment is affected if Paid Memberships Pro version 0.7.2 or below is installed AND the Add Member From Admin functionality is accessible AND no CSRF nonce validation is present in that form.
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 · scopedUpdate Paid Memberships Pro to version 0.7.3 or later to obtain the security patch that implements anti-CSRF token validation on the affected admin forms.
Update to the latest version of Paid Memberships Pro - Add Member From Admin plugin (version > 0.7.2)
- Check the current version of the Paid Memberships Pro - Add Member From Admin plugin installed on your WordPress site
- Navigate to Plugins > Add New in the WordPress admin dashboard
- Search for "Paid Memberships Pro - Add Member From Admin"
- Update the plugin to the latest available version (any version above 0.7.2)
- Verify the update was successful by checking the installed version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57659 — 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-2026-57659 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