dbcve.org
Tutor LmsWordPress extension · Themeum

CVE-2024-5784

HIGH · 7.1 CVSS v3.1 Published 2024-08-30
Fix available
A fix is available. Upgrade to 2.7.3 or later.
See remediation →
77/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 Pro plugin for WordPress is vulnerable to unauthorized administrative actions execution due to a missing capability checks on multiple functions like treport_quiz_atttempt_delete and tutor_gc_class_action in all versions up to, and including, 2.7.2. This makes it possible for authenticated attackers, with the subscriber-level access and above, to preform an administrative actions on the site, like comments, posts or users deletion, viewing notifications, etc.

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 lacks proper capability/authorization checks on multiple administrative functions (treport_quiz_attempt_delete and tutor_gc_class_action). Authenticated users with subscriber-level permissions can execute these functions to delete comments, posts, or users, and view administrative notifications.

MitigationUpdate Tutor LMS Pro to version 2.7.3 or later which adds proper capability checks to the affected functions. If unable to update immediately, restrict subscriber-level account creation as a temporary mitigation.

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.3

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm Tutor LMS is installed and active
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Themeum Tutor LMS' or 'Tutor LMS'. Verify it shows as 'Active'.
    Affected if The plugin is installed and active, exposing the vulnerable functions.
  2. Identify the installed Tutor LMS version
    In WordPress admin, go to Plugins > Installed Plugins. Click on 'View details' next to Tutor LMS, or check the plugin header in wp-content/plugins/tutor/*.php for the 'Version' comment.
    Affected if The installed version is any version prior to 2.7.3 (e.g., 2.7.2, 2.7.1, 2.6.x, etc.).
  3. Check for subscriber-level user accounts
    In WordPress admin, go to Users > All Users. Review the 'Role' column for any accounts assigned the 'Subscriber' role.
    Affected if At least one user account exists with the Subscriber role, which can exploit the vulnerability.
  4. Verify the vulnerable AJAX actions are accessible
    Inspect page source or use browser developer tools to check if admin-ajax.php responds to actions 'treport_quiz_attempt_delete' or 'tutor_gc_class_action' when called by a low-privilege user. Alternatively, grep for these action names in the plugin files under wp-content/plugins/tutor/.
    Affected if These AJAX actions are present and accessible without proper capability checks.

A user is affected if Tutor LMS version is below 2.7.3 AND subscriber-level user accounts exist in WordPress, allowing unauthorized administrative actions.

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.3 or later
Fixed in 2.7.3
Interim mitigation

Update Tutor LMS Pro to version 2.7.3 or later which adds proper capability checks to the affected functions. If unable to update immediately, restrict subscriber-level account creation as a temporary mitigation.

Recommended fix High confidence

Tutor LMS version 2.7.3

  1. Backup your WordPress database and files before making any changes
  2. Log in to your WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Locate the Tutor LMS plugin in the list
  5. If an update is available, click 'Update Now' to upgrade to version 2.7.3
  6. Alternatively, navigate to Dashboard > Updates and select Tutor LMS to update
  7. Verify the plugin version after updating to confirm version 2.7.3 is installed
  8. Test that Tutor LMS functionality works correctly after the update

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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