Skip to main content
VulnerabilityPublished

CVE-2026-5167: Masteriyo LMS (WordPress plugin) · Insecure Direct Object Reference

Affects Masteriyo LMS (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium.

Data as of 30 Oct 2026, 06:59 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Apr 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 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
masteriyoMasteriyo LMS – Online Course Builder for eLearning, LMS & EducationAffected
  • <=2.1.7
Fixed in–

AI-suggested

Until an official fix is available, administrators should ensure that the webhook_secret setting is properly configured with a strong secret value and verify that the HTTP_STRIPE_SIGNATURE header is required and validated. If possible, restrict access to the webhook endpoint to trusted IP addresses or implement additional verification controls. Monitor vendor channels for updates or patches addressing this vulnerability.

Description

Masteriyo LMS plugin for WordPress versions up to 2.1.7 contains an authorization bypass vulnerability due to insufficient webhook signature verification. The webhook endpoint processes unauthenticated requests and only verifies signatures if a webhook_secret is configured and the HTTP_STRIPE_SIGNATURE header is present. Since webhook_secret defaults to an empty string, attackers can send unauthenticated fake Stripe webhook events with arbitrary order_id values, marking orders as completed without payment and gaining unauthorized access to paid course content.

References

Community reviews

Loading reviews…