Paid Membership SubscriptionsWordPress extension · Cozmoslabs
CVE-2023-51522
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 Cozmoslabs Paid Member Subscriptions.This issue affects Paid Member Subscriptions: from n/a through 2.10.4.
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 Cozmoslabs Paid Member Subscriptions WordPress plugin allows attackers to trick authenticated users into performing unintended actions such as modifying subscription settings, changing user roles, or processing payments without their consent.
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 Membership SubscriptionsWordPress extension
<= 2.10.4CVSS 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.
-
Locate the Paid Membership Subscriptions plugin versionIn WordPress admin, go to Plugins > Installed Plugins and find 'Paid Membership Subscriptions' by Cozmoslabs. The version number is displayed below the plugin name. Alternatively, check the main plugin file (wp-content/plugins/paid-member-subscriptions/index.php) and look for the 'Version' header in the plugin comments.Affected if The displayed version number is 2.10.4 or lower.
-
Confirm the plugin is activeIn WordPress admin under Plugins > Installed Plugins, verify that 'Paid Membership Subscriptions' shows as 'Active' rather than 'Inactive'.Affected if The plugin is active and the version is 2.10.4 or lower.
-
Verify access to subscription management featuresLog in as a subscriber-level user and attempt to access any page that allows modifying subscription settings, changing user roles, or initiating payments (such as the account page, subscription upgrade/downgrade page, or checkout pages).Affected if The plugin is active at a vulnerable version and these subscription management pages are accessible to authenticated users.
Your environment is affected if the Paid Membership Subscriptions plugin is active and the installed version is 2.10.4 or lower, allowing authenticated users to access subscription modification features without CSRF protection.
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.
From vendor dataImplement anti-CSRF tokens (nonces) on all state-changing forms and validate these tokens server-side before processing requests; also consider SameSite cookie attributes as an additional layer of protection.
Fix this in Paid Membership Subscriptions
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-2023-51522 — 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-2023-51522 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