Simple MembershipWordPress extension · Simple Membership Plugin
CVE-2016-10884
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 · uneditedThe simple-membership plugin before 3.3.3 for WordPress has multiple CSRF issues.
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 confidenceThe simple-membership WordPress plugin before version 3.3.3 contains multiple Cross-Site Request Forgery (CSRF) vulnerabilities. CSRF attacks trick authenticated users into executing unintended actions on a web application, potentially allowing attackers to modify plugin settings, add or delete users, or alter membership configurations without the legitimate user's 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
Simple MembershipWordPress extension
< 3.3.3CVSS 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.
-
Check installed plugin version via WordPress adminNavigate to Plugins > Installed Plugins in the WordPress admin dashboard. Locate 'Simple Membership' or 'Simple WP Membership' in the list and read the version number displayed beneath the plugin name.Affected if The version listed is lower than 3.3.3 (for example, 3.3.2, 3.3.1, 3.3.0, or any earlier version).
-
Verify version via plugin main fileAccess the plugin directory via FTP or file manager at wp-content/plugins/simple-membership/simple-membership.php. Open the main PHP file and locate the 'Version' header in the plugin comment block at the top of the file.Affected if The Version field shows a number less than 3.3.3.
-
Confirm plugin is activeIn the WordPress admin under Plugins > Installed Plugins, verify that the Simple Membership plugin shows as 'Active' (not just installed).Affected if The plugin is active AND the version is below 3.3.3 - only active instances can be exploited via CSRF.
If the Simple Membership plugin is active and the installed version is any version prior to 3.3.3, the environment is affected by CVE-2016-10884.
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 data3.3.3
Update the simple-membership plugin to version 3.3.3 or later to patch the CSRF vulnerabilities. Additionally, ensure WordPress core and all other plugins are kept current.
Fix this in Simple Membership
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2016-10884 — 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-2016-10884 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