dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-39524

HIGH · 7.5 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Unauthenticated Broken Access Control in Masteriyo - LMS <= 2.1.5 versions.

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

Unauthenticated broken access control vulnerability in Masteriyo WordPress LMS plugin versions 2.1.5 and earlier. An unauthenticated attacker can access resources or perform actions that should require proper authorization, likely due to missing capability checks or insecure direct object references in the plugin's functionality.

MitigationUpdate Masteriyo LMS to the latest version (newer than 2.1.5) which should contain proper access control fixes. If immediate update is not possible, restrict access to the affected endpoints via web server configuration or disable the plugin temporarily.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Identify Masteriyo LMS plugin version
    Access the WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate Masteriyo LMS, and note the version number displayed. Alternatively, inspect the main plugin PHP file in wp-content/plugins/masteriyo/ for the Version header in the plugin comment block, or check the readme.txt file.
    Affected if The installed version is 2.1.5 or earlier (any version up to and including 2.1.5)
  2. Compare version to affected range
    If you cannot access the WordPress admin, use file system access to read the plugin header. The version string is typically found in the main plugin file (e.g., masteriyo.php) under the plugin name comment block, or in readme.txt under the 'Stable tag' field.
    Affected if The version cannot be determined or is not newer than 2.1.5, meaning the plugin is in the affected range
  3. Test for unauthenticated endpoint access
    Send HTTP requests to common Masteriyo AJAX endpoints (such as wp-admin/admin-ajax.php with masteriyo_ actions) without providing authentication cookies or credentials. Use curl or a web proxy to observe the response.
    Affected if The endpoints return successful responses (HTTP 200 with data) instead of requiring login or returning authorization errors (HTTP 401/403)
  4. Review plugin configuration for capability enforcement
    Inspect the plugin source code files in wp-content/plugins/masteriyo/ for capability check functions. Look for proper use of current_user_can() or similar authorization checks before sensitive operations, particularly in files handling user data or administrative functions.
    Affected if Code review reveals missing or insufficient capability checks before sensitive operations, indicating the access control flaw is present

If the Masteriyo LMS plugin version is 2.1.5 or earlier and unprotected endpoints are accessible without authentication, the environment is affected by this vulnerability

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Masteriyo LMS to the latest version (newer than 2.1.5) which should contain proper access control fixes. If immediate update is not possible, restrict access to the affected endpoints via web server configuration or disable the plugin temporarily.

Recommended fix Moderate confidence

Masteriyo LMS version 2.1.6 or later

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to the WordPress admin dashboard > Plugins > Installed Plugins.
  3. 3. Find Masteriyo - LMS in the plugin list.
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version.
  5. 5. Alternatively, download the latest version from the WordPress Plugin Repository and upload it manually.
  6. 6. After updating, verify the plugin version shows 2.1.6 or later in the plugins list.
  7. 7. Test critical LMS functions (course creation, enrollment, lesson access) to confirm the update did not break functionality.

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

Have this fixed 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 help mitigating

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-2026-39524 — 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-2026-39524 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