CVE-2026-82849: Masteriyo LMS WordPress plugin insecure direct object reference in course progress

CVE-2026-82849 · Severity: medium · CVSS 4.3 · Published 2026-09-24

Masteriyo LMS is a WordPress plugin that manages online courses and student learning activities. The plugin fails to verify that users can only access their own course progress records, allowing any logged-in subscriber to view the learning activity of other students. In the worst case, an attacker can retrieve the progress records of all learners on the site at once.

Vendors: Masteriyo.

Quick answers

Is CVE-2026-82849 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-82849 being exploited in the wild.
How severe is CVE-2026-82849?
Medium severity, with a CVSS score of 4.3, published 24 September 2026.
Which products and versions are affected?
Masteriyo LMS before 3.4.2.
Is there a fix for CVE-2026-82849?
A patch was published on 2026-09-24: Version 3.4.2 fixes the vulnerability Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-82849 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-82849?
Check whether you run Masteriyo LMS at an affected version. 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

An insecure direct object reference (IDOR) vulnerability exists in the course progress endpoint due to missing ownership validation. Authenticated users can access course progress records of other users by exploiting the missing or bypassable authorization check, particularly when no specific user account ID is provided. The vulnerability requires authentication but affects any user role including self-registered subscribers.

Affected products

  • Masteriyo Masteriyo LMS before 3.4.2

Timeline

  • 2026-09-22: disclosed
  • 2026-09-24: patched: Version 3.4.2 fixes the vulnerability

References

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