dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-13766

MEDIUM · 5.4 CVSS v3.1 Published 2026-01-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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
The MasterStudy LMS WordPress Plugin – for Online Courses and Education plugin for WordPress is vulnerable to unauthorized modification and deletion of data due to a missing capability checks on multiple REST API endpoints in all versions up to, and including, 3.7.6. This makes it possible for authenticated attackers, with Subscriber-level access and above, to upload or delete arbitrary media files, delete or modify posts, and create/manage course templates

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 · high confidence

The MasterStudy LMS WordPress plugin lacks proper capability checks on multiple REST API endpoints, allowing any authenticated user with Subscriber-level access (the lowest privilege) to perform privileged actions including uploading/deleting arbitrary media files, deleting/modifying posts, and creating/managing course templates.

MitigationUpdate the plugin to version 3.7.7 or later which contains proper capability checks on REST API endpoints. Until patched, consider disabling user registrations or implementing additional firewall rules to restrict API access.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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. Confirm MasterStudy LMS plugin is installed
    In the WordPress admin dashboard, go to Plugins > Installed Plugins and look for 'MasterStudy LMS' in the list. Note whether it is active or inactive.
    Affected if The plugin is installed and active in the WordPress environment
  2. Identify the installed plugin version
    On the Plugins page, click on the plugin name or view details to display the version number. Alternatively, check the plugin header in /wp-content/plugins/masterstudy-lms/main.php for the 'Version' tag.
    Affected if The version number is lower than 3.7.7 (the fixed version)
  3. Verify if user registration is enabled
    In WordPress admin, go to Settings > General and check if 'Membership' is enabled with 'Anyone can register' selected. Also check what default role is assigned to new users.
    Affected if User registration is enabled and allows new users to register at the Subscriber level or above
  4. Test REST API endpoint access with low-privilege account
    Create a test user with Subscriber role if not already present. Use a tool like curl or Postman to send a request to the MasterStudy REST API endpoints (such as /wp-json/masterstudy/v1/media_upload or /wp-json/masterstudy/v1/posts) using the Subscriber credentials.
    Affected if The API returns successful responses (200 OK) instead of 401/403 authentication errors, indicating the endpoints accept requests from low-privilege users

The environment is affected if MasterStudy LMS is active, the version is below 3.7.7, and the vulnerable REST API endpoints are accessible to authenticated users with Subscriber-level permissions.

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 the plugin to version 3.7.7 or later which contains proper capability checks on REST API endpoints. Until patched, consider disabling user registrations or implementing additional firewall rules to restrict API access.

Recommended fix Moderate confidence

Upgrade MasterStudy LMS to version 3.7.7 or later

  1. Backup your WordPress database and files before making any changes
  2. Navigate to Dashboard > Plugins in WordPress admin
  3. Locate MasterStudy LMS in the plugins list
  4. Click 'Update now' if an update is available, or manually upload version 3.7.7 or later
  5. After updating, verify the plugin version shows 3.7.7 or higher in the plugins list
  6. Test that REST API endpoints now properly enforce capability checks (Subscriber users should no longer be able to modify/delete arbitrary content or upload files outside their permissions)

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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