dbcve.org
Tutor LmsWordPress extension · Themeum

CVE-2024-4222

HIGH · 8.2 CVSS v3.1 Published 2024-05-16
Fix available
A fix is available. Upgrade to 2.7.1 or later.
See remediation →
91/100
Remediation priority · Urgent
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
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 multiple functions in all versions up to, and including, 2.7.0. This makes it possible for unauthenticated attackers to add, modify, or delete user meta and plugin options.

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 WordPress plugin versions up to 2.7.0 contains a critical authorization flaw where multiple functions lack proper capability checks, allowing unauthenticated attackers to add, modify, or delete user metadata and plugin options. This missing authorization validation permits any visitor to perform privileged administrative actions.

MitigationUpgrade to Tutor LMS Pro version 2.7.1 or later immediately, as this version includes the necessary capability checks (proper use of current_user_can() or equivalent authorization functions) on the affected functions.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/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. Check Tutor LMS Pro version
    In WordPress admin, go to Plugins > Installed Plugins > TutorLMS and view the version number, or inspect the main plugin file header in wp-content/plugins/tutor/ for the 'Version' field
    Affected if Version is 2.7.0 or lower (any version below 2.7.1)
  2. Confirm plugin is active
    Verify the Tutor LMS plugin is enabled on the site through WordPress admin Plugins page
    Affected if Plugin is installed and active
  3. Identify functions lacking capability checks
    Review plugin source code for AJAX handlers or callback functions that handle user_metadata or option updates; look for missing current_user_can() or similar authorization calls before sensitive operations
    Affected if Code contains functions that modify user_metadata or plugin_options without capability verification
  4. Test for unauthenticated metadata modification
    Send a direct request to known plugin AJAX endpoints (such as wp-admin/admin-ajax.php) with action parameters related to user metadata without providing authentication cookies
    Affected if Requests succeed and modify user data without login credentials
  5. Test for unauthenticated option modification
    Send direct requests to plugin AJAX endpoints that handle plugin settings or options without authentication
    Affected if Plugin settings or options can be changed by unauthenticated visitors

Your environment is affected if Tutor LMS Pro version is below 2.7.1 and the plugin is active, with unauthenticated users able to modify user metadata or plugin options through exposed functions.

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

Upgrade to Tutor LMS Pro version 2.7.1 or later immediately, as this version includes the necessary capability checks (proper use of current_user_can() or equivalent authorization functions) on the affected functions.

Recommended fix High confidence

Tutor LMS Pro version 2.7.1 or later

  1. 1. Back up your WordPress site before making any changes.
  2. 2. Navigate to the WordPress admin dashboard.
  3. 3. Go to Plugins > Installed Plugins.
  4. 4. Find 'Tutor LMS Pro' in the plugin list.
  5. 5. If an update is available, click 'Update Now' to upgrade to version 2.7.1 or higher.
  6. 6. Alternatively, download the latest version from the official Themeum marketplace or WordPress repository and upload it manually.
  7. 7. After updating, verify the plugin version shows 2.7.1 or later in the Plugins list.
  8. 8. Test critical Tutor LMS functionality (course creation, user enrollment, settings) to confirm the update did not break existing functionality.
Caveat Standard minor/pro point release - minimal risk of breaking changes expected, but test in staging first as a precaution

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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