CVE-2023-3105

LearnDash LMS <= 4.6.0 - Authenticated (Subscriber+) Insecure Direct Object Reference to Arbitrary User Password Change

2023-06-27 00:00
István Márton

Strategic Overview

Status
Patched in 4.6.0.1
Affected Plugin
LearnDash LMS
Affected Version
<= 4.6.0
CVSS
8.8High
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2023-3105
View all LearnDash LMS vulnerabilities

At a glance

CVE-2023-3105 is a high-severity Authorization Bypass Through User-Controlled Key vulnerability in the LearnDash LMS WordPress plugin, affecting versions <= 4.6.0. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 4.6.0.1; sites on affected versions should update now. Disclosed June 2023, reported by István Márton.

Vulnerability Overview

The 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 Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in LearnDash LMS <= 4.6.0 takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For LearnDash LMS the fix is 4.6.0.1: builds <= 4.6.0 are affected, anything from 4.6.0.1 onward is not.

Remediation

Update to version 4.6.0.1, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: LearnDash LMS 4.6.0.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C