dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-64209

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 masterstudy allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Masterstudy: from n/a through < 4.8.122.

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 WordPress plugin allows unauthenticated attackers to access functionality that should be restricted by access control lists (ACLs). This broken access control issue enables users to perform actions without proper privilege verification.

MitigationUpdate Masterstudy plugin to version 4.8.122 or later to receive the vendor patch that adds proper authorization checks. If immediate update is not possible, restrict access to affected endpoints at the web server level.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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. Verify Masterstudy plugin is installed
    Navigate to WordPress admin dashboard under Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'masterstudy'
    Affected if The Masterstudy plugin is found in the WordPress installation
  2. Check installed Masterstudy version
    In WordPress admin, go to Plugins > Masterstudy LMS and view the version number, or check the main plugin file header in /wp-content/plugins/masterstudy/lms.php for the 'Version' tag
    Affected if The installed version is lower than 4.8.122 (vulnerable)
  3. Identify accessible REST API or AJAX endpoints
    Inspect the plugin directory for registered REST API routes (typically in includes/ or endpoints/ folders) and check if any admin-only actions are hooked to wp_ajax_nopriv_ or rest_api_init without capability checks
    Affected if REST routes or AJAX actions intended for logged-in administrators are hooked without proper authorization checks and are accessible to unauthenticated users
  4. Review access logs for unauthorized Masterstudy endpoint access
    Search web server access logs (Apache/nginx) for requests to /wp-admin/admin-ajax.php, /wp-json/masterstudy/, or plugin-specific endpoints originating from unauthenticated IPs
    Affected if Unauthenticated requests successfully reach endpoints that should require administrator privileges
  5. Test ACL bypass by accessing protected functionality
    Submit a request to Masterstudy plugin admin functions (such as course creation, user management, or settings modification) without providing authentication credentials
    Affected if The action completes or returns success without requiring login

The environment is affected if Masterstudy LMS plugin version is below 4.8.122 AND the plugin is active AND unauthenticated users can reach ACL-protected functionality.

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 plugin to version 4.8.122 or later to receive the vendor patch that adds proper authorization checks. If immediate update is not possible, restrict access to affected endpoints at the web server level.

Recommended fix Moderate confidence

Masterstudy version 4.8.122 or higher

  1. 1. Update the Masterstudy theme/plugin to version 4.8.122 or later
  2. 2. Verify the update was successful by checking the version number in the WordPress admin panel
  3. 3. Test the affected functionality to confirm the authorization controls are now properly enforced

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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