dbcve.org
MasteriyoWordPress extension

CVE-2024-43239

HIGH · 8.1 CVSS v3.1 Published 2024-08-18
Fix available
A fix is available. Upgrade to 1.11.5 or later.
See remediation →
87/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
Authorization Bypass Through User-Controlled Key vulnerability in masteriyo Masteriyo - LMS learning-management-system.This issue affects Masteriyo - LMS: from n/a through <= 1.11.4.

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 authorization bypass vulnerability in the Masteriyo WordPress LMS plugin allows attackers to manipulate user-controlled key parameters to bypass authentication/authorization checks, potentially gaining unauthorized access to LMS features or data. The vulnerability exists in versions through 1.11.4.

MitigationUpdate Masteriyo - LMS to the latest version after vendor patch is released. In the interim, restrict access to the WordPress admin panel and monitor for suspicious access patterns.

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

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
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Verify Masteriyo LMS plugin is installed
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'Masteriyo - LMS' or 'Masteriyo' in the plugin list
    Affected if The plugin is present in the WordPress installation
  2. Check installed version number
    In the plugins list, find Masteriyo and note the version number displayed under the plugin name. Alternatively, inspect the plugin's main PHP file header or check the version in wp-content/plugins/masteriyo/readme.txt
    Affected if Version is 1.11.4 or lower (any version through 1.11.4)
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify the Masteriyo plugin shows as 'Active' (not just installed)
    Affected if Plugin is activated and running on the site
  4. Audit access logs for suspicious parameter manipulation
    Review web server access logs (Apache/Nginx) and WordPress audit logs for requests to LMS endpoints containing unexpected or manipulated key parameters, especially those occurring outside normal admin workflows
    Affected if Unusual requests to LMS functionality with modified parameters are found in logs

Your site is affected if Masteriyo LMS plugin versions 1.11.4 or below are installed and active on your WordPress 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.11.5 or later
Fixed in 1.11.5
Interim mitigation

Update Masteriyo - LMS to the latest version after vendor patch is released. In the interim, restrict access to the WordPress admin panel and monitor for suspicious access patterns.

Recommended fix High confidence

Masteriyo LMS version 1.11.5

  1. Backup your WordPress site and database before proceeding
  2. Log in to your WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Find Masteriyo LMS in the plugin list
  5. If an update is available, click 'Update Now' to update to version 1.11.5 or later
  6. Alternatively, download version 1.11.5 from the official WordPress plugin repository or your account on masteriyo.com
  7. Deactivate the existing Masteriyo plugin, then delete it, and install the fresh version 1.11.5
  8. Verify the update was successful by checking the plugin version in Plugins > Installed Plugins

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

Fix this in Masteriyo Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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