Uncanny Groups For LearndashWordPress extension · Uncannyowl
CVE-2024-8349
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 Uncanny Groups for LearnDash plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 6.1.0.1. This is due to the plugin not properly restricting what users a group leader can edit. This makes it possible for authenticated attackers, with group leader-level access and above, to change admin account email addresses which can subsequently lead to admin account access.
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 Uncanny Groups for LearnDash WordPress plugin fails to properly restrict editing capabilities for group leader users, allowing them to modify admin account email addresses. This improper authorization check enables authenticated group leaders to escalate privileges by changing admin credentials through email modification.
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
Uncanny Groups For LearndashWordPress extension
< 6.1.1CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Verify plugin installation and versionIn WordPress admin, go to Plugins > Installed Plugins and find 'Uncanny Groups for LearnDash' by Uncannyowl. Note the installed version number.Affected if The plugin version is installed and is lower than 6.1.1 (e.g., 6.1.0, 6.0.x, etc.)
-
Confirm group leader role existsGo to Users > Users List in WordPress admin. Look for users with the 'Group Leader' role assigned. Can also check via Users > User Roles if the role is visible.Affected if Any user account has the Group Leader role assigned in WordPress
-
Check for unauthorized admin modificationsReview admin account email addresses in Users > Users List. Compare current admin emails against known legitimate values or check WordPress site audit logs for recent email changes on administrator accounts.Affected if Any admin account email address has been changed without authorization
-
Inspect plugin capability settingsNavigate to LearnDash LMS > Groups > Group Management or the plugin settings page to review what user roles group leaders are permitted to edit.Affected if Group leaders have permission to edit or modify administrator-level accounts
The environment is affected if the Uncanny Groups for LearnDash plugin version is below 6.1.1 AND there are group leader users configured in the system who could potentially modify admin credentials.
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 · scoped6.1.1
Update the plugin to a patched version beyond 6.1.0.1 that properly enforces access control restrictions on which user roles group leaders can edit.
Uncanny Groups for LearnDash version 6.1.1
- Backup your WordPress site before making any changes
- Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- Find 'Uncanny Groups for LearnDash' in the plugin list
- Click 'Update now' if an update is available, or manually upload version 6.1.1 or later
- Verify the plugin version shows 6.1.1 or higher after updating
- Test that group leader permissions are working correctly and cannot modify admin accounts
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Uncanny Groups For Learndash
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8349 — 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-2024-8349 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