MembersonicWordPress extension
CVE-2016-10971
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 MemberSonic Lite plugin before 1.302 for WordPress has incorrect login access control because only knowlewdge of an e-mail address is required.
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 confidenceThe MemberSonic Lite WordPress plugin before version 1.302 contains an authentication bypass vulnerability where the login mechanism can be exploited using only knowledge of a valid email address, allowing unauthenticated attackers to gain unauthorized access to user accounts without knowing the corresponding password.
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
MembersonicWordPress extension
< 1.302CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm MemberSonic Lite plugin is installedNavigate to WordPress admin dashboard > Plugins section and look for 'MemberSonic Lite' in the list of installed pluginsAffected if MemberSonic Lite appears in the installed plugins list
-
Identify installed plugin versionIn the Plugins list, locate MemberSonic Lite and note the version number displayed beneath the plugin nameAffected if Version number is visible and is less than 1.302
-
Cross-check via plugin filesIf available, inspect the plugin main file (typically membersonic-lite.php or similar) in wp-content/plugins/ and look for the 'Version' header commentAffected if Version header shows a number lower than 1.302
-
Verify plugin is activeIn WordPress admin > Plugins, confirm the MemberSonic Lite plugin is activated (not just installed)Affected if Plugin status shows as 'Active'
Your environment is affected if MemberSonic Lite plugin is installed and active with a version number below 1.302, as this combination allows the authentication bypass to be exploited using only a valid email address.
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 · scoped1.302
Update the MemberSonic Lite plugin to version 1.302 or later to remediate this vulnerability; alternatively, disable or remove the plugin if not needed.
MemberSonic Lite version 1.302
- Backup your WordPress site database and files before making any changes
- Navigate to WordPress admin dashboard > Plugins section
- Locate the MemberSonic Lite plugin
- Update the plugin to version 1.302 or later
- Verify the update was successful and test login functionality
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Membersonic
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10971 — 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-10971 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