CVE-2026-16310: MemberDash <= 1.8.5 - Unauthenticated Account Takeover via Insecure Direct Object Reference via 'id' Parameter
The MemberDash plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.8.5 via the 'id' parameter due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to change the password of any WordPress user, including administrators, by supplying an arbitrary user ID during registration, and take over their account without any notification sent to the victim.
Security readout for executives and security teams
Plain-English summary
An unauthenticated attacker may reset any WordPress user’s password, including an administrator’s, on sites running MemberDash through version 1.8.5. Successful abuse could give the attacker full site control without notifying the victim.
Executive priority
Treat as an emergency for internet-accessible sites running MemberDash 1.8.5 or earlier. Rapidly inventory, contain, and follow vendor remediation guidance because successful exploitation may enable silent administrator takeover and complete website compromise.
Technical view
MemberDash reportedly fails to validate that a user-controlled id parameter belongs to the person registering. This CWE-639 insecure direct object reference allows unauthenticated password changes for arbitrary WordPress accounts. The supplied CVSS 3.1 score is 9.8 because exploitation is remote, low-complexity, requires no privileges or user interaction, and may compromise confidentiality, integrity, and availability.
Likely exposure
WordPress sites using MemberDash 1.8.5 or earlier are potentially exposed, particularly where the affected registration functionality is reachable from the internet. The bundle does not identify required configuration, reliable inventory indicators, or affected endpoint details.
Exploitation context
The described flaw is remotely exploitable without authentication or victim interaction. However, the CVE is not listed as KEV in the supplied bundle, and no supplied source confirms active exploitation, public proof-of-concept availability, or observed attacks.
Researcher notes
The narrative states all versions through 1.8.5 are affected, but the structured affected entry lists version "0" with defaultStatus "unaffected." Treat the narrative range as the working indicator while confirming vendor data. No patch version, endpoint, exploit evidence, or compromise indicators are supplied; avoid active testing against production.
Mitigation direction
Identify all WordPress sites running MemberDash and record installed versions.
Check LearnDash or MemberDash guidance for a confirmed fixed release or vendor mitigation.
Prioritize updating vulnerable installations after validating the vendor-provided release.
If no fix is available, disable MemberDash or restrict affected registration access where operationally acceptable.
Reset affected credentials and review administrator accounts if compromise is suspected.
Validation and detection
Confirm MemberDash is absent or newer than the vendor-confirmed affected range.
Verify the installed release against current LearnDash or MemberDash security guidance.
Review recent password changes, new administrators, and unexpected privilege modifications.
Check authentication and application logs for suspicious unauthenticated registration activity.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
4Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-639 · source CWE mapping
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.