CVE-2026-89333

Tutor LMS <= 4.0.8 - Insecure Direct Object Reference to Authenticated (Subscriber+) Sensitive Information Exposure via 'student_id' Parameter

2026-09-18 14:02
Dthangws

Strategic Overview

Status
Patched in 4.0.9
Affected Version
<= 4.0.8
CVSS
6.5Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-89333
View all Tutor LMS – eLearning and online course solution vulnerabilities

At a glance

CVE-2026-89333 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Tutor LMS WordPress plugin, affecting versions <= 4.0.8. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 4.0.9; sites on affected versions should update now. Disclosed September 2026, reported by Dthangws.

Vulnerability Overview

The Tutor LMS – eLearning and online course solution plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 4.0.8 via the 'student_id' parameter due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with subscriber-level access and above, to disclose the email address and Tutor profile phone number of arbitrary WordPress users, including Administrators, by iterating over user IDs via the student_id parameter.

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.

CWE-639: Authorization Bypass Through User-Controlled Key

Tutor LMS <= 4.0.8 carries this weakness at student_id, and reaching it 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 Tutor LMS the fix is 4.0.9: builds <= 4.0.8 are affected, anything from 4.0.9 onward is not.

Remediation

Update to version 4.0.9, 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: Tutor LMS 4.0.9 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