dbcve.org
MasteriyoWordPress extension · Themegrill

CVE-2024-33939

MEDIUM · 5.3 CVSS v3.1 Published 2025-05-19
Fix available
A fix is available. Upgrade to 1.7.4 or later.
See remediation →
62/100
Remediation priority · Elevated
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
Authentication Bypass Using an Alternate Path or Channel vulnerability in masteriyo Masteriyo - LMS learning-management-system.This issue affects Masteriyo - LMS: from n/a through <= 1.7.3.

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

This is an authentication bypass vulnerability in the Masteriyo WordPress LMS plugin. The 'alternate path or channel' classification indicates that unauthenticated attackers can access protected functionality through some secondary mechanism - likely an unprotected API endpoint, admin AJAX handler, or similar endpoint that doesn't properly validate user identity. An attacker could potentially access or manipulate course content, user data, or administrative functions without valid credentials.

MitigationUpdate Masteriyo LMS to the latest patched version as soon as available; until then, consider restricting access to the plugin's endpoints via web server configuration or deploying a WAF rule to monitor for anomalous 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.7.4

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Locate Masteriyo plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for the 'masteriyo' folder, or query the WordPress database in wp_options for option_name 'active_plugins' to see if masteriyo is listed
    Affected if The Masteriyo plugin folder exists or is listed in active plugins
  2. Determine installed version
    Read the 'Version' header from the main plugin file (wp-content/plugins/masteriyo/masteriyo.php) or check the WordPress plugins admin page
    Affected if Version number is lower than 1.7.4
  3. Compare against affected range
    Verify the installed version against the vulnerable range: versions prior to 1.7.4 are affected
    Affected if Installed version is less than 1.7.4 (e.g., 1.7.3, 1.6.0, etc.)
  4. Identify unprotected endpoints
    Inspect the plugin directory for REST API routes (typically in includes/routes/ or similar), AJAX handlers (admin-ajax.php calls), or other public endpoints that may lack capability checks. Use a web scanner or manually probe common paths such as /wp-json/masteriyo/v1/ or admin-ajax?action=masteriyo_*
    Affected if Unprotected API endpoints or AJAX handlers exist that allow unauthenticated access to administrative or sensitive functions

A user is affected if Masteriyo LMS version is below 1.7.4 AND the vulnerable unauthenticated endpoint is accessible in their environment.

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.4 or later
Fixed in 1.7.4
Interim mitigation

Update Masteriyo LMS to the latest patched version as soon as available; until then, consider restricting access to the plugin's endpoints via web server configuration or deploying a WAF rule to monitor for anomalous access patterns.

Recommended fix High confidence

1.7.4

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Masteriyo - LMS' in the plugin list
  4. Click 'Update now' if an update is available, or manually update to version 1.7.4
  5. Verify the plugin version is now 1.7.4 or higher after the update completes
  6. Test that authentication functionality works correctly

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

Fix this in Masteriyo Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
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,152.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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