MasteriyoWordPress extension · Themegrill

CVE-2024-24882

CRITICAL · 9.8 CVSS v3.1 Published 2024-05-17
Fix available
A fix is available. Upgrade to 1.7.3 or later.
See remediation →
100/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
Incorrect Privilege Assignment vulnerability in masteriyo Masteriyo - LMS learning-management-system.This issue affects Masteriyo - LMS: from n/a through <= 1.7.2.

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

An Incorrect Privilege Assignment vulnerability in the Masteriyo WordPress LMS plugin (versions <=1.7.2) allows unauthenticated or low-privileged users to escalate their privileges to administrative levels, likely through improper validation of user roles during registration or course enrollment processes.

MitigationUpdate Masteriyo - LMS to the latest patched version immediately. Until patched, disable new user registrations and review existing user role assignments in the WordPress admin dashboard.

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
MasteriyoWordPress extension
Affected:< 1.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify if Masteriyo LMS plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Masteriyo - LMS' or check the plugin files in /wp-content/plugins/ for a masteriyo directory
    Affected if The Masteriyo plugin is present on the WordPress site
  2. Determine the installed Masteriyo version
    In WordPress admin, go to Plugins > Installed Plugins and click on Masteriyo to view the version number, or check the main plugin file header for the Version field
    Affected if The installed version is 1.7.2 or lower (anything below 1.7.3)
  3. Verify if WordPress user registration is enabled
    In WordPress admin, go to Settings > General and check 'Membership: Anyone can register' is checked, or query the site via WP-CLI: wp option get users_can_register
    Affected if User registration is enabled and Masteriyo version is vulnerable
  4. Review existing user accounts for unauthorized administrators
    In WordPress admin, go to Users > All Users and examine the list for administrator accounts you did not create, or use WP-CLI: wp user list --role=administrator
    Affected if There are administrator accounts that were not created by known administrators

You are affected if Masteriyo LMS plugin version 1.7.2 or lower is installed AND user registration is enabled on the site.

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 1.7.3 or later
Fixed in 1.7.3
Interim mitigation

Update Masteriyo - LMS to the latest patched version immediately. Until patched, disable new user registrations and review existing user role assignments in the WordPress admin dashboard.

Recommended fix Moderate confidence

1.7.3

  1. Backup your WordPress site and database before updating
  2. Update Masteriyo LMS plugin to version 1.7.3 or later via WordPress admin: go to Plugins > Installed Plugins > find Masteriyo LMS > click Update Now
  3. Alternatively, download version 1.7.3 from WordPress.org and upload via FTP if auto-update is unavailable
  4. Verify successful update by confirming the plugin shows version 1.7.3 or higher in the Plugins list
  5. Test that the LMS functionality (courses, lessons, quizzes) continues to work correctly after the update

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

Fix this in Masteriyo 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 the upgrade done

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-2024-24882 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-24882 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