dbcve.org
Tutor LmsWordPress extension · Themeum

CVE-2024-4351

HIGH · 8.8 CVSS v3.1 Published 2024-05-16
Fix available
A fix is available. Upgrade to 2.7.1 or later.
See remediation →
94/100
Remediation priority · Urgent
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 Pro plugin for WordPress is vulnerable to unauthorized access of data, modification of data, loss of data due to a missing capability check on the 'authenticate' function in all versions up to, and including, 2.7.0. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to gain control of an existing administrator account.

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 Pro plugin for WordPress versions up to 2.7.0 lacks a capability check on its 'authenticate' function, allowing authenticated users with subscriber-level permissions to invoke administrative functions and take control of existing administrator accounts.

MitigationUpdate Tutor LMS Pro to version 2.7.1 or later. If patching is not immediately possible, disable the plugin or restrict user registration until the update can be applied.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Tutor LmsWordPress extension
Affected:< 2.7.1

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Confirm Tutor LMS Pro plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Tutor LMS' or 'Tutor LMS Pro' in the list
    Affected if Plugin is present and active in the WordPress installation
  2. Check installed Tutor LMS version
    In the plugins list, click on 'View details' next to Tutor LMS or check the plugin header comments in /wp-content/plugins/tutor/ folder for the version number
    Affected if Version is less than 2.7.1 (for example, 2.7.0, 2.6.x, etc.)
  3. Verify if user registration is enabled
    Go to WordPress admin > Settings > General and check 'Anyone can register' is ticked, or inspect wp_options table for 'users_can_register' option set to 1
    Affected if User registration is enabled and new subscriber-level accounts can be created
  4. Check for existing subscriber-level user accounts
    Navigate to WordPress admin > Users and review the list for users with 'Subscriber' role, or query the wp_usermeta table for meta_key='wp_capabilities' containing 'subscriber'
    Affected if At least one subscriber-level user account exists in the system

A user is affected if Tutor LMS Pro version is below 2.7.1, the plugin is active, and either subscriber-level users exist or user registration is enabled allowing such accounts to be created.

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
Upgrade available Upgrade to 2.7.1 or later
Fixed in 2.7.1
Interim mitigation

Update Tutor LMS Pro to version 2.7.1 or later. If patching is not immediately possible, disable the plugin or restrict user registration until the update can be applied.

Recommended fix High confidence

Tutor LMS Pro version 2.7.1

  1. Backup your WordPress site database and files before making any changes
  2. Navigate to the WordPress admin dashboard > Plugins section
  3. Locate the Tutor LMS Pro plugin in the installed plugins list
  4. Click 'Update now' if an update to version 2.7.1 or later is available, or manually upload version 2.7.1 if the automatic update is not showing
  5. After updating, verify the plugin version shows 2.7.1 or higher under Plugins > Installed Plugins
  6. Test that the Tutor LMS functionality is working correctly (create a course, enroll a student, etc.)
  7. Ensure no unauthorized administrator accounts have been created by checking Users > All Users in WordPress admin

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

Fix this in Tutor Lms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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