dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-40743

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Unauthenticated Broken Access Control in Tutor LMS <= 3.9.7 versions.

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 · moderate confidence

Unauthenticated broken access control vulnerability in Tutor LMS plugin for WordPress versions 3.9.7 and below allows remote attackers to access sensitive functionality or perform privileged actions without authentication due to missing or insufficient capability checks on certain endpoints.

MitigationUpdate Tutor LMS to a version newer than 3.9.7 when available; if a patched version is not yet released, consider temporarily disabling the plugin or implementing web server-level access restrictions to mitigate exposure.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

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

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 is installed
    Check WordPress plugin directory for tutor-lms folder, or view installed plugins in WordPress admin under Plugins > Installed Plugins
    Affected if Tutor LMS plugin files exist in /wp-content/plugins/ directory
  2. Determine installed version
    Read the main plugin file (tutor.php or tutor-lms.php) and look for 'Version:' in the plugin header comment, or check the version displayed next to the plugin name in WordPress admin Plugins page
    Affected if Version is 3.9.7 or lower (e.g., 3.9.6, 3.9.5, 3.0, etc.)
  3. Confirm plugin is active
    Check WordPress admin under Plugins > Installed Plugins - the plugin status should show as 'Active'
    Affected if Tutor LMS shows as Active with version 3.9.7 or below

User is affected if Tutor LMS plugin version 3.9.7 or below is installed and active on their WordPress site, as the missing capability checks exist in the plugin code itself for certain endpoints.

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 Tutor LMS to a version newer than 3.9.7 when available; if a patched version is not yet released, consider temporarily disabling the plugin or implementing web server-level access restrictions to mitigate exposure.

Recommended fix Moderate confidence

Tutor LMS 3.9.8 or latest stable release

  1. Check your current Tutor LMS version in WordPress admin under Plugins
  2. If running Tutor LMS version 3.9.7 or lower, navigate to Plugins > Add New > Upload Plugin (or use WordPress plugin repository)
  3. Download and install the latest stable version of Tutor LMS from the official WordPress plugin repository
  4. Verify the new version is installed and active
  5. Test critical LMS functions (course creation, student enrollment, quiz attempts) to confirm proper operation
  6. Review user role permissions to confirm access controls are functioning correctly
Caveat Minor release; verify compatibility with your WordPress version and other installed addons

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40743 — 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-40743 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