LearnDash LMS: Authorization Bypass Through User-Controlled Key
CVE-2023-3105 is a high-severity authorization bypass through user-controlled key vulnerability in LearnDash LMS from StellarWP, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected LearnDash LMS versions: 4.6.0 and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 2.23% chance of exploitation within 30 days, higher than 83% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of LearnDash LMS you run against the affected versions below, and install the vendor's latest release.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| StellarWP | LearnDash LMS | 4.6.0 and earlier | Not stated |
| Learndash | Learndash | 4.6.0 and earlier | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (wordfence.com).
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Authorization Bypass Through User-Controlled Key
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
How developers prevent this class of flaw
- For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
- Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
- Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.
More Authorization Bypass Through User-Controlled Key vulnerabilities (CWE-639)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- learndash.com/release-notes/Release Notes
Third-party and government advisories
Other vulnerabilities in LearnDash LMS
- 7.5 High severity
Recent Authorization Bypass Through User-Controlled Key vulnerabilities
- 9.8 Critical severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 7.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.