Skip to main content
VulnerabilityPublished

CVE-2026-5060: MasterStudy LMS WordPress Plugin – for Online Courses and Education · Insecure Direct Object Reference

Affects MasterStudy LMS WordPress Plugin – for Online Courses and EducationSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 27 Oct 2026, 05:11 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
stylemixMasterStudy LMS WordPress Plugin – for Online Courses and EducationAffected
  • <=3.7.23
Fixed in–

AI-suggested

Until a fix is available, restrict Instructor-level access to trusted users only. Monitor for plugin updates from stylemix addressing this vulnerability and apply official patches once released.

Description

The MasterStudy LMS WordPress Plugin for Online Courses and Education is affected by an insecure direct object reference vulnerability in all versions up to and including 3.7.14. This vulnerability allows authenticated users with Instructor-level access or higher to delete arbitrary attachments belonging to any user by exploiting a lack of ownership validation in the deletion function. The issue arises from the stm_lms_delete_cover() function not verifying the ownership of the file_id parameter before calling wp_delete_attachment().

References

Community reviews

Loading reviews…