dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-64214

HIGH · 7.5 CVSS v3.1 Published 2025-12-18
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
Missing Authorization vulnerability in StylemixThemes MasterStudy LMS Pro masterstudy-lms-learning-management-system-pro allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects MasterStudy LMS Pro: from n/a through < 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 MasterStudy LMS Pro WordPress plugin allows unauthenticated or unauthorized users to access functionality that should be restricted by access control lists (ACLs). The specific function and attack vector are not detailed, but the vulnerability exists in versions prior to 4.7.16.

MitigationUpdate MasterStudy LMS Pro to version 4.7.16 or later to apply the authorization fix. Review user roles and permissions in the LMS after updating to confirm access controls are functioning correctly.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Verify MasterStudy LMS Pro is installed
    Check your WordPress installation for the MasterStudy LMS Pro plugin in wp-content/plugins/ or via WordPress admin under Plugins
    Affected if The plugin is installed and active in WordPress
  2. Identify the installed version
    Locate the main plugin file (typically masterstudy-lms-learning-management-system-pro.php) and read the Version header comment, or check the Plugins page in WordPress admin for the version number
    Affected if A version number is displayed that is lower than 4.7.16
  3. Compare version to affected range
    Compare your installed version to the known affected versions: any version prior to 4.7.16 is vulnerable
    Affected if Your installed version is below 4.7.16 (for example, 4.7.15, 4.7.14, etc.)
  4. Confirm plugin is active
    Verify the plugin status in WordPress admin under Plugins - the plugin must be active for the authorization flaw to be exploitable
    Affected if The plugin shows as Active and your version is below 4.7.16

You are affected if MasterStudy LMS Pro is installed and active with a version lower than 4.7.16, as the missing authorization vulnerability can be exploited by unauthenticated or unauthorized users.

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 apply the authorization fix. Review user roles and permissions in the LMS after updating to confirm access controls are functioning correctly.

Recommended fix Moderate confidence

4.7.16 or later

  1. Backup your WordPress site and database before updating
  2. Update MasterStudy LMS Pro to version 4.7.16 or later via the WordPress admin dashboard, theme panel, or by uploading the new version
  3. Clear any caching mechanisms after the update
  4. Verify the plugin updated successfully by checking the version number in the WordPress admin
  5. Test that the previously vulnerable functionality is now properly protected by authorization controls
Caveat Review the MasterStudy LMS Pro changelog between your current version and 4.7.16 for any feature changes or compatibility notices before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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