dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-64366

HIGH · 7.6 CVSS v3.1 Published 2025-10-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Stylemix MasterStudy LMS masterstudy-lms-learning-management-system allows Blind SQL Injection.This issue affects MasterStudy LMS: from n/a through <= 3.6.27.

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

A blind SQL injection vulnerability exists in the MasterStudy LMS WordPress plugin. The vulnerability allows unauthenticated attackers to inject malicious SQL queries through unsanitized user input, potentially enabling data exfiltration or authentication bypass. Blind SQL injection means the attacker infers information from application behavior differences rather than seeing direct database output.

MitigationApply the vendor patch immediately upon release. In the interim, restrict access to the affected endpoints via web application firewall rules or disable the vulnerable functionality if possible.

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/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. Verify MasterStudy LMS plugin is installed
    Check for the plugin directory at /wp-content/plugins/masterstudy-lms-learning-management-system/ or view installed plugins in WordPress admin under Plugins
    Affected if The plugin directory or listing shows MasterStudy LMS is present on the site
  2. Determine the installed plugin version
    Read the main plugin file (e.g., masterstudy.php) to find the 'Version' header, or check the WordPress plugin admin page for the installed version number
    Affected if The installed version is lower than the patched version released to address CVE-2025-64366
  3. Confirm the plugin is active
    Check WordPress admin under Plugins > Installed Plugins to see if MasterStudy LMS is activated, or query the wp_options table for the active_plugins option
    Affected if The plugin is currently active and accessible to unauthenticated users
  4. Identify exposed user input endpoints
    Review the plugin's public-facing PHP files in the /includes/ or /controllers/ directories for $_GET, $_POST, or $_REQUEST usage without proper sanitization or prepare() statements
    Affected if Unsantized user-supplied parameters are accepted by the plugin's frontend or AJAX endpoints

If MasterStudy LMS is installed and active, the site is potentially affected unless the specific version includes the vendor patch for CVE-2025-64366.

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

Apply the vendor patch immediately upon release. In the interim, restrict access to the affected endpoints via web application firewall rules or disable the vulnerable functionality if possible.

Recommended fix Moderate confidence

Upgrade to MasterStudy LMS version 3.6.28 or later

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find MasterStudy LMS in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. After updating, verify the version number reflects the fixed release (3.6.28 or later)
  6. 6. Test critical LMS functionality to ensure the update did not break existing features
Caveat Standard minor version upgrades for WordPress plugins typically do not introduce breaking changes, but test in staging first if possible

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,320
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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