Skip to main content
VulnerabilityPublished Updated

CVE-2026-19712: Masteriyo LMS (WordPress plugin) · Cross-Site Scripting (XSS)

Affects Masteriyo LMS (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.1 Medium : upgrade to 2.3.3 when convenient.

Data as of 14 Nov 2026, 20:44 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.3.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 14 Nov 2026.

What to do

Upgrade Masteriyo LMS (WordPress plugin) to 2.3.3.

Affected software

ProductAffectedFixed in
Masteriyo LMSAffected
  • <2.3.3
Fixed in
  • 2.3.3

AI-suggested

Users should upgrade to Masteriyo LMS version 2.3.3 or later once available. In the meantime, multisite installations or defining DISALLOW_UNFILTERED_HTML can mitigate the risk by removing the capability that allows unfiltered HTML storage by instructors.

Description

The Masteriyo LMS WordPress plugin before 2.3.3 does not sanitise and escape a quiz field before outputting it back in a page, and grants its instructor role the ability to store unfiltered HTML, allowing such users to perform Stored Cross-Site Scripting attacks against any visitor of the affected page, including administrators. This affects default single-site installations. Sites running multisite, or defining DISALLOW_UNFILTERED_HTML, are not affected as the capability is not granted there.

References

Community reviews

Loading reviews…