WordPress security changelog
MEDIUM CVE-2026-5167 Deferred

Masteriyo LMS – Online Course Builder for eLearning, LMS & Education: A security weakness

Masteriyo LMS – Online Course Builder for eLearning, LMS & Education is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is <= 2.1.7.

CVE / CNA score 5.3 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Masteriyo LMS – Online Course Builder for eLearning, LMS & Education
Plugin slug
learning-management-system
Affected
<= 2.1.7
Safe version
See mitigation notes
Published
Apr 08, 2026
Weakness
CWE-639 — Authorization Bypass Through User-Controlled Key

This CVE was published Apr 08, 2026 and is one of 19 known issues for this plugin.

What to do

Update, patch or deactivate.

No fixed release is identified. Update Masteriyo LMS – Online Course Builder for eLearning, LMS & Education when a release after 2.1.7 becomes available; until then, disable and remove it when the site's risk warrants. The official upstream changelog lists version 2.3.3, which is newer than the published affected range. Its changelog does not clearly confirm this specific fix, so it is not counted as a known-safe release.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

The Masteriyo LMS – Online Course Builder for eLearning, LMS & Education plugin for WordPress is vulnerable to Authorization Bypass Through User-Controlled Key in versions up to and including 2.1.7. This is due to insufficient webhook signature verification in the handle_webhook() function. The webhook endpoint processes unauthenticated requests and only performs signature verification if both the webhook_secret setting is configured AND the HTTP_STRIPE_SIGNATURE header is present. Since webhook_secret defaults to an empty string, the webhook processes attacker-controlled JSON payloads without any verification. This makes it possible for unauthenticated attackers to send fake Stripe webhook events with arbitrary order_id values in the metadata, mark any order as completed without payment, and gain unauthorized access to paid course content.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

References

Primary and upstream sources