dbcve.org
Masterstudy LmsWordPress extension · Stylemixthemes

CVE-2024-1512

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-17
Fix available
A fix is available. Upgrade to after 3.2.5 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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
The MasterStudy LMS WordPress Plugin – for Online Courses and Education plugin for WordPress is vulnerable to union based SQL Injection via the 'user' parameter of the /lms/stm-lms/order/items REST route in all versions up to, and including, 3.2.5 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 fails to properly sanitize the 'user' parameter in the /lms/stm-lms/order/items REST API endpoint, allowing unauthenticated attackers to inject arbitrary SQL queries via union-based SQL injection. The vulnerability stems from insufficient input escaping and lack of parameterized queries in the SQL construction.

MitigationUpgrade MasterStudy LMS plugin to version 3.2.6 or later. If immediate upgrade is not possible, consider temporarily disabling the REST API endpoint or restricting access at the web server level.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Masterstudy LmsWordPress extension
Affected:<= 3.2.5

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Identify MasterStudy LMS plugin installation
    Check your WordPress plugins directory or WP Admin plugins list for 'Masterstudy Lms' or 'MasterStudy LMS' plugin
    Affected if The plugin is installed and active on the WordPress site
  2. Determine installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > MasterStudy LMS and note the version number displayed. Alternatively, check the plugin's main PHP file (typically in wp-content/plugins/masterstudy-lms/main.php) for the 'Version' header in the plugin comment block
    Affected if The version is 3.2.5 or lower
  3. Verify vulnerable REST API endpoint is accessible
    Send a GET request to /wp-json/lms/stm-lms/order/items or /?rest_route=/lms/stm-lms/order/items using a tool like curl or Burp Suite. Check if the endpoint responds (HTTP 200 or other) rather than returning 404 or forbidden
    Affected if The endpoint returns any response indicating it exists and is reachable
  4. Test parameter handling on vulnerable endpoint
    Send a request to the endpoint with a test 'user' parameter value, for example: /wp-json/lms/stm-lms/order/items?user=test. Observe if the parameter is accepted and processed without immediate error
    Affected if The endpoint accepts the 'user' parameter and processes it without rejecting the input

If MasterStudy LMS version 3.2.5 or lower is installed AND the /lms/stm-lms/order/items REST API endpoint is accessible and accepts the 'user' parameter, the environment is likely affected by CVE-2024-1512.

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
Upgrade available Upgrade to a release after 3.2.5
Interim mitigation

Upgrade MasterStudy LMS plugin to version 3.2.6 or later. If immediate upgrade is not possible, consider temporarily disabling the REST API endpoint or restricting access at the web server level.

Recommended fix High confidence

3.2.6 or latest available version

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find MasterStudy LMS in the plugin list
  4. Check if an update is available for MasterStudy LMS
  5. Update to the latest version which contains the security fix

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

Fix this in Masterstudy Lms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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