CVE-2026-88844: MasterStudy LMS insecure direct object reference in course enrollment data

CVE-2026-88844 · Severity: low · CVSS 2.7 · Published 2026-09-18

MasterStudy LMS is a WordPress plugin that enables instructors to manage online courses and track student enrollment. A flaw in versions before 3.7.50 allows any instructor to view the names and email addresses of students enrolled in other instructors' courses by exploiting missing access controls. This exposes sensitive student information and violates privacy expectations.

Quick answers

Is CVE-2026-88844 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-88844 being exploited in the wild.
How severe is CVE-2026-88844?
Low severity, with a CVSS score of 2.7, published 18 September 2026.
Which products and versions are affected?
MasterStudy LMS 3.6.2 to before 3.7.50.
Is there a fix for CVE-2026-88844?
A patch was published on 2026-09-18: fixed in version 3.7.50 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-88844 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-88844?
Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is an insecure direct object reference (IDOR) in the course enrollment data endpoint. The plugin fails to verify that the requesting instructor owns a course before returning enrolled-student information, allowing an authenticated instructor to enumerate and retrieve student PII from courses they do not manage. The attack requires an active instructor account but no additional user interaction; the attacker can directly request student data for any course ID. The vulnerability is fixed in version 3.7.50 and later.

Affected products

  • MasterStudy LMS 3.6.2 to before 3.7.50

Timeline

  • 2026-09-16: disclosed
  • 2026-09-18: patched: fixed in version 3.7.50

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.