Masterstudy LmsWordPress extension · Stylemixthemes
CVE-2024-37093
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Stylemix MasterStudy LMS masterstudy-lms-learning-management-system allows Cross Site Request Forgery.This issue affects MasterStudy LMS: from n/a through <= 3.2.1.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the MasterStudy LMS WordPress plugin allows remote attackers to induce authenticated users to perform unintended actions by tricking them into submitting malicious requests. The plugin fails to properly validate anti-CSRF tokens (nonces) on state-changing operations such as form submissions and AJAX requests.
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
< 3.2.2CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify MasterStudy LMS installationIn WordPress admin, go to Plugins > Installed Plugins and locate 'MasterStudy LMS - Online Learning, Course Management LMS'. Note the version number displayed. Alternatively, check the plugin main PHP file (typically /wp-content/plugins/masterstudy-lms/) for the version defined in the plugin header comment.Affected if Plugin is installed with version lower than 3.2.2 (e.g., 3.2.1, 3.2.0, earlier versions)
-
Locate state-changing formsInspect plugin PHP files that handle form submissions. Look for files containing form handlers, particularly in /classes/ or /controllers/ directories. Search for $_POST or $_GET handling that processes user input without subsequent nonce verification.Affected if Forms exist that process state-changing requests (user registrations, course enrollments, profile updates) without calling wp_verify_nonce() or check_ajax_referer()
-
Verify nonce field presence in formsExamine frontend form templates (.phtml or .php files in /views/ or /templates/ directories). Search for calls to wp_nonce_field() or wp_create_nonce() before form closing tags. Check AJAX JavaScript files for nonce inclusion in request data.Affected if Forms or AJAX handlers that submit state-changing data lack nonce fields (wp_nonce_field) in their markup or nonce parameter in their request payloads
-
Inspect AJAX action handlersReview files registering AJAX endpoints (add_action('wp_ajax_...')). Verify that each handler calls check_ajax_referer() or wp_verify_nonce() early in the function before processing the request.Affected if AJAX action handlers process requests without verifying nonce validity, allowing forged requests from other sites
You are affected if the MasterStudy LMS plugin version is below 3.2.2 AND your site processes state-changing requests (form submissions or AJAX calls) through this plugin without proper nonce validation.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.2.2
Implement WordPress nonces (wp_nonce_field) on all forms and AJAX actions, verify nonce validation in request handlers, and validate Origin/Referer headers to ensure requests originate from trusted sources.
MasterStudy LMS version 3.2.2
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find MasterStudy LMS in the plugin list
- Check if an update to version 3.2.2 or higher is available
- If an update is available, click 'Update Now' to apply the security patch
- After updating, verify the plugin version shows 3.2.2 or newer in the plugins list
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Masterstudy Lms
Scoped from the published advisory
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37093 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-37093 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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