CVE-2026-1375

Tutor LMS <= 3.9.5 - Insecure Direct Object Reference to Authenticated (Instructor+) Arbitrary Course Modification and Deletion

Strategic Overview

Status
Patched in 3.9.6
Affected Version
<= 3.9.5
CVSS
8.1High
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-1375
View all Tutor LMS – eLearning and online course solution vulnerabilities

At a glance

CVE-2026-1375 is a high-severity Authorization Bypass Through User-Controlled Key vulnerability in the Tutor LMS WordPress plugin, affecting versions <= 3.9.5. It carries a CVSS score of 8.1 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires an authenticated account at Instructor level or above. The issue is fixed in version 3.9.6; sites on affected versions should update now. Disclosed February 2026, reported by Athiwat Tiprasaharn (Jitlada).

Vulnerability Overview

The Tutor LMS – eLearning and online course solution plugin for WordPress is vulnerable to Insecure Direct Object References (IDOR) in all versions up to, and including, 3.9.5. This is due to missing object-level authorization checks in the `course_list_bulk_action()`, `bulk_delete_course()`, and `update_course_status()` functions. This makes it possible for authenticated attackers, with Tutor Instructor-level access and above, to modify or delete arbitrary courses they do not own by manipulating course IDs in bulk action requests.

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 integrity, availability.

CWE-639: Authorization Bypass Through User-Controlled Key

Tutor LMS <= 3.9.5 carries this weakness at course_list_bulk_action(), and reaching it takes an account at Instructor 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 3.9.6: builds <= 3.9.5 are affected, anything from 3.9.6 onward is not.

Remediation

Update to version 3.9.6, 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 3.9.6 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