LearnDash MemberDash
MemberDash <= 1.8.7 - Authenticated (Subscriber+) Privilege Escalation to Administrator via Edit Profile 'id' Parameter
The MemberDash plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.8.7. This is due to a mass-assignment vulnerability in the `user_account_manager()` function's edit_profile branch, where all submitted `$_POST` fields are iterated and directly assigned to the current member object via the `MS_Model` `__set()` magic method with no field allowlist and no capability or ownership check on the submitted `id` parameter. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject an arbitrary user ID via the `id` parameter — overwriting any WordPress user's email address and password, including the site administrator's — and subsequently use those modified credentials to gain full administrative access to the site.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- <= 1.8.7
Mitigation
The record names no fix. Check the vendor advisory below.
References
- Release notes docs.nexcess.com/software/changelogs/learndash/membe…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.1 pending · 2 not a PoC · 1 suspicious or fake
Pending 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| cmivqa/ro-arxiv-daily | 18 Sep 2024 −2.2 y | 1 | Pending · repository exceeds size limit
Flags · score 5
Below the suspicion threshold (50); does not change the assessment. |
Not a PoC 2
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| Noorts/duckdb-changelog | 2 Oct 2025 −1.1 y | 0 | Not a PoC · unrelated |
| jaschadub/compromised-packages-check | 20 May 2026 −178 d | 1 | Not a PoC · unrelated
Flags · score 35
Below the suspicion threshold (50); does not change the assessment. |
Suspicious or fake 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| GHLists/new-cves | 24 Sep 2026 −51 d | 0 | Suspicious · score 60
Why suspicious
|
Only PoCs count toward the first-PoC date and the characteristics below. Suspicious repositories (score ≥ 50) never count. Do not run PoC code from unknown sources.