CVE-2026-57694

Tutor LMS – eLearning and online course solution <= 3.9.13 - Unauthenticated Insecure Direct Object Reference

2026-07-06 00:00
TristanInSec

Strategic Overview

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

At a glance

CVE-2026-57694 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Tutor LMS WordPress plugin, affecting versions <= 3.9.13. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.9.14; sites on affected versions should update now. Disclosed July 2026, reported by TristanInSec.

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, 3.9.13 due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to perform an unauthorized action.

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.

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in Tutor LMS <= 3.9.13 takes no account at all. 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.14: builds <= 3.9.13 are affected, anything from 3.9.14 onward is not.

Remediation

Update to version 3.9.14, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Tutor LMS 3.9.14 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