LearndashWordPress extension
CVE-2023-3105
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 LearnDash LMS plugin for WordPress is vulnerable to Insecure Direct Object References in versions up to, and including, 4.6.0. This is due to the plugin providing user-controlled access to objects, letting a user bypass authorization and access system resources. This makes it possible for attackers with with existing account access at any level, to change user passwords and potentially take over administrator accounts.
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 LearnDash LMS WordPress plugin up to version 4.6.0 contains an Insecure Direct Object Reference (IDOR) vulnerability that allows authenticated users at any privilege level to bypass authorization checks and access/modify other users' passwords, potentially leading to admin account takeover.
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
LearndashWordPress extension
<= 4.6.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify installed LearnDash versionIn WordPress admin, navigate to Plugins > Installed Plugins and locate LearnDash LMS. The version number is displayed under the plugin name. Alternatively, check the main plugin file (wp-content/plugins/sfwd-lms/sfwd_lms.php) for the 'Version' header.Affected if The installed version is 4.6.0 or lower.
-
Verify password modification endpoint existsCheck if the LearnDash password change functionality is accessible. Inspect the plugin files for any AJAX handlers or form handlers that process password change requests for users. Look for files in the plugin directory that handle user profile or password updates.Affected if The plugin handles password changes and the endpoint exists in version 4.6.0 or lower.
-
Confirm user privilege handlingReview the LearnDash plugin code for functions that process password modification requests. Check if there are authorization checks before allowing password changes for other users. Look for functions handling user ID parameters in password reset or update operations.Affected if The code processes user IDs in password operations without proper privilege validation in version 4.6.0 or lower.
-
Check for user enumeration exposureTest or inspect whether the plugin exposes user IDs or allows sequential access to user data that could enable an attacker to identify valid user accounts for password modification attempts.Affected if User identifiers are exposed or predictable in version 4.6.0 or lower, enabling IDOR exploitation.
Your environment is affected if the installed LearnDash LMS plugin version is 4.6.0 or lower and the password modification functionality is present and accessible to authenticated users.
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 · scopedUpdate the LearnDash LMS plugin to a version beyond 4.6.0. Verify the update resolves the IDOR vulnerability and test that core LMS functionality (courses, quizzes, user management) continues to work correctly after the update.
Latest LearnDash LMS version (greater than 4.6.0)
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate the LearnDash LMS plugin in the list
- 4. If an update is available, click 'Update Now' to install the latest version
- 5. Alternatively, download the latest version from the official WordPress plugin repository or LearnDash website
- 6. After updating, verify the new version number is installed correctly
- 7. Test that user functionality works properly, particularly user password changes and administrative functions
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Learndash
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-2023-3105 — 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-2023-3105 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