CVE-2024-37093

4.3 MEDIUM

📋 TL;DR

A Cross-Site Request Forgery (CSRF) vulnerability in the MasterStudy LMS WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions. This affects all WordPress sites running MasterStudy LMS version 3.2.1 and earlier. The vulnerability requires an authenticated user to be tricked into clicking a malicious link.

💻 Affected Systems

Products:
  • MasterStudy LMS WordPress Plugin
Versions: n/a through 3.2.1
Operating Systems: All operating systems running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: All WordPress installations using vulnerable versions of MasterStudy LMS are affected regardless of configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

An attacker could trick an administrator into changing plugin settings, creating/editing courses, or potentially modifying user roles and permissions.

🟠

Likely Case

Attackers could create spam courses, modify existing content, or change basic plugin configuration settings through forged requests.

🟢

If Mitigated

With proper CSRF protections, no unauthorized actions can be performed even if users click malicious links.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: LOW

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

CSRF attacks require social engineering to trick authenticated users into clicking malicious links or visiting compromised sites.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 3.2.2 or later

Vendor Advisory: https://patchstack.com/database/wordpress/plugin/masterstudy-lms-learning-management-system/vulnerability/wordpress-masterstudy-lms-wordpress-plugin-plugin-3-2-1-cross-site-request-forgery-csrf-vulnerability?_s_id=cve

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins → Installed Plugins. 3. Find MasterStudy LMS and click 'Update Now'. 4. Verify update completes successfully.

🔧 Temporary Workarounds

Implement CSRF Protection Headers

all

Add Content Security Policy headers to help prevent CSRF attacks

Add to .htaccess: Header set Content-Security-Policy "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src 'self' 'unsafe-inline'"

🧯 If You Can't Patch

  • Restrict plugin access to trusted administrators only and implement strict access controls
  • Use browser extensions that block CSRF attempts and educate users about phishing risks

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin → Plugins → Installed Plugins for MasterStudy LMS version

Check Version:

wp plugin list --name=masterstudy-lms --field=version

Verify Fix Applied:

Verify MasterStudy LMS version is 3.2.2 or higher in WordPress plugins list

📡 Detection & Monitoring

Log Indicators:

  • Unusual plugin configuration changes from unexpected IP addresses
  • Multiple failed CSRF token validations in WordPress logs

Network Indicators:

  • POST requests to MasterStudy LMS endpoints without proper referrer headers
  • Requests containing suspicious parameters to plugin admin pages

SIEM Query:

source="wordpress.log" AND ("masterstudy" OR "MasterStudy LMS") AND ("csrf" OR "invalid nonce" OR "security check failed")

🔗 References

📤 Share & Export