Missing AuthorizationWeakness · CWE-862

CVE-2025-64215

MEDIUM · 6.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 →
74/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
Missing Authorization vulnerability in StylemixThemes MasterStudy LMS Pro allows Accessing Functionality Not Properly Constrained by ACLs. This issue affects MasterStudy LMS Pro: from n/a before 4.7.16.

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

Missing authorization vulnerability in the MasterStudy LMS Pro WordPress plugin allows authenticated users to access functionality that is not properly constrained by access control lists. This is likely a broken access control (BAC) issue where privilege checks are missing on certain functions or AJAX endpoints, potentially allowing lower-privileged users to perform administrative or instructor-level actions.

MitigationUpdate MasterStudy LMS Pro to version 4.7.16 or later to receive the vendor patch that adds proper authorization checks. If immediate update is not possible, disable the plugin until patched.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

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 MasterStudy LMS Pro is installed
    Check the WordPress plugins directory or use WP-CLI: wp plugin list --name='masterstudy-lms-learning-management-system-pro'
    Affected if The plugin is present on the WordPress site
  2. Identify the installed plugin version
    Check the plugin header in /wp-content/plugins/masterstudy-lms-learning-management-system-pro/masterstudy.php or use: wp plugin get masterstudy-lms-learning-management-system-pro --field=version
    Affected if Version is below 4.7.16 (the fixed release)
  3. Verify lower-privileged user accounts exist
    List user roles on the site using: wp user list --role=subscriber OR wp user list --role=student OR check Users > All Users in WordPress admin for non-administrator roles
    Affected if Any user roles below administrator or instructor exist on the site
  4. Test for accessible AJAX endpoints
    If authenticated as a lower-privileged user (subscriber/student), attempt to access common plugin AJAX actions by inspecting plugin JavaScript files for wp_ajax_ hooks or checking if non-admin users can trigger instructor-level actions
    Affected if Lower-privileged users can access endpoints that should require instructor or administrator privileges

The environment is affected if MasterStudy LMS Pro version is below 4.7.16 and the site contains user accounts with roles below administrator or instructor.

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 MasterStudy LMS Pro to version 4.7.16 or later to receive the vendor patch that adds proper authorization checks. If immediate update is not possible, disable the plugin until patched.

Recommended fix Moderate confidence

4.7.16

  1. 1. Identify the currently installed version of the MasterStudy LMS Pro plugin in WordPress
  2. 2. Create a complete backup of the WordPress site (database and files) before proceeding with any updates
  3. 3. Update MasterStudy LMS Pro to version 4.7.16 or later through the WordPress plugin admin interface or via FTP
  4. 4. Confirm the update was successful by verifying the installed version number
  5. 5. Test critical LMS functionality including course creation, user enrollment, and admin access controls to verify the authorization fix is working

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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