dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-1375

HIGH · 8.1 CVSS v3.1 Published 2026-02-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Tutor LMS WordPress plugin lacks object-level authorization checks in the course management functions (course_list_bulk_action, bulk_delete_course, update_course_status). Authenticated attackers with Tutor Instructor role can manipulate course IDs in bulk action requests to modify or delete courses they do not own, exploiting an IDOR vulnerability.

MitigationUpdate to version 3.9.6 or later which contains proper authorization validation. Until then, restrict the Tutor Instructor role to trusted users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Tutor LMS plugin is installed
    Check your WordPress installation under wp-content/plugins/tutor-lms/ or view the installed plugins in the WordPress admin dashboard
    Affected if Tutor LMS plugin is present in the WordPress installation
  2. Check the installed Tutor LMS version
    Look in the plugin header (version field) in wp-content/plugins/tutor-lms/index.php or in WordPress admin > Plugins > Tutor LMS
    Affected if The installed version matches the affected version range for this vulnerability (compare to any available patched version)
  3. Identify users with Tutor Instructor role
    In WordPress admin, go to Users and filter by Tutor Instructor role, or query wp_usermeta for meta_key='tutor_instructor'
    Affected if Any user account has Tutor Instructor-level permissions
  4. Verify vulnerable bulk action functions exist
    Examine the Tutor LMS source code in includes/*.php for functions course_list_bulk_action(), bulk_delete_course(), and update_course_status() and check if they include ownership verification before processing
    Affected if These functions exist without proper authorization/ownership checks on the course IDs being processed

A user is affected if Tutor LMS is installed, they have Tutor Instructor-level access, and the vulnerable bulk action functions lack proper object-level authorization checks before allowing course modification or deletion.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 3.9.6 or later which contains proper authorization validation. Until then, restrict the Tutor Instructor role to trusted users only.

Recommended fix Moderate confidence

Upgrade to Tutor LMS version 3.9.6 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the Tutor LMS plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to version 3.9.6 or later
  5. 5. After updating, verify the plugin version shows 3.9.6 or higher under Plugins > Installed Plugins

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1375 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1375 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data