On this page (7 sections)
A critical vulnerability, tracked as CVE-2026-124990, affects the Masteriyo LMS (LMS Course Builder, Quizzes & Certificates) plugin for WordPress in versions up to and including 3.5.1. The NVD record describes a PHP Object Injection weakness in the plugin's course importer.
If you run an online course site on WordPress with this plugin, check your version and your registration and checkout settings now. Whether an anonymous visitor can reach the flaw depends on configuration, which is explained below.
What happened
The vulnerability was published in the NVD on 2026-11-18. According to the record, the plugin's course importer deserializes untrusted data. Specifically, the set_post_metas() method calls maybe_unserialize() on attacker-controlled postmeta string values taken from an uploaded JSON import file. That lets an attacker inject arbitrary PHP objects into the application.
Only one independent publisher, the NVD entry, covers this story so far. The record references a Wordfence threat intelligence entry and the plugin's code on WordPress.org Trac, including a 3.5.2 tag. The research does not state which release fixes the issue, so confirm that against the plugin changelog before relying on it.
Technical details in plain terms
PHP can turn objects into a text format (serialization) and rebuild them later (unserialization). If an application rebuilds objects from data an attacker controls, the attacker can choose which object types get created. What happens next depends on which classes exist in the codebase and its libraries. This weakness class is CWE-502, deserialization of untrusted data.
Here the untrusted input is the JSON file used by the course import feature. The NVD description lists code paths in the importer, the REST API import/export controller and the checkout code as references. The record does not describe what an attacker can ultimately achieve, and this article does not speculate beyond it.
Who is actually exposed
The record separates two situations, and the difference matters for triage.
Unauthenticated attackers (non-default setup)
Exploitation without an account requires all of the following at once:
- enable_instructor_registration is set to true
- enable_guest_checkout is set to true
- At least one purchasable course exists
The record notes that Install.php sets enable_instructor_registration to false on fresh installs, so this is a non-default configuration. Sites that turned on open instructor registration and guest checkout to sell courses are the ones to look at first.
Default installations
On a default installation, the record says the flaw requires an attacker with author-level access or above. That is a lower risk, but it still matters if you allow public author or contributor-style sign-ups, have many staff accounts, or reuse weak passwords.
How to check your exposure
Start with the installed plugin version. This WP-CLI command lists the plugin and its version; run it from your WordPress root. The plugin directory slug, learning-management-system, comes from the Trac URLs in the record.
wp plugin list --name=learning-management-system --fields=name,status,versionIf the version is 3.5.1 or lower, you are in the affected range. Then review the two settings that decide whether anonymous exploitation is possible. In the WordPress admin, check the Masteriyo settings for instructor registration and guest checkout. The option names in the record are enable_instructor_registration and enable_guest_checkout, but the research does not give their exact location in the settings screens.
You can also review your user list for unexpected author-level or instructor accounts.
wp user list --role=author --fields=ID,user_login,user_email,user_registeredWhat to do now
- Run the version check above on every site that uses Masteriyo LMS.
- Update the plugin to the latest release from the WordPress plugin directory. Check the changelog to confirm the release addresses CVE-2026-124990, since the research does not name the fixed version.
- If you cannot update immediately, turn off open instructor registration and guest checkout where your business allows it.
- Review author-level and instructor accounts. Remove ones you do not recognize and reset passwords for any you doubt.
- Restrict who can use the course import feature to administrators you trust.
- Take a backup before updating, then test course pages, checkout and imports afterward.
- Look through web server logs for unexpected requests to the plugin's import endpoints and for unusual file uploads.
Detection and monitoring
The research reports no confirmed exploitation, and nothing in it describes indicators of compromise. That means you cannot rule out misuse by checking for a known signature, so focus on general signs: new administrator or author accounts, modified or unfamiliar PHP files in wp-content, unexpected scheduled tasks, and import requests you did not make.
A search through access logs can show who has been calling import routes. Adjust the log path to your server; this looks for the word import in request lines and is read-only.
grep -i "import" /var/log/nginx/access.log | grep -i "POST" | tail -n 50Review the output for POST requests from unfamiliar IP addresses, especially from visitors with no account. For wider hygiene, see the WordPress security checklist and the guide on whether a plugin is vulnerable. You can also look up plugin issues on the WordPress plugin vulnerabilities page.
If you suspect a site was already abused, follow the steps in website hacked: what to do.
Timeline
| Date | Event |
|---|---|
| 2026-11-18 | CVE-2026-124990 published in the NVD with a CVSS score of 9.8 |
| Not stated | Fixed version and exploitation status are not given in the research |
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
