Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-112329 Overview
CVE-2026-112329 is a broken access control vulnerability [CWE-862] in the Sensei LMS WordPress plugin before version 4.26.4. The flaw resides in the legacy save_new_message handler hooked on the init action. The handler validates only a generic nonce and does not verify course enrollment or restrict post_id to valid post types. Authenticated attackers with Subscriber-level access can supply an arbitrary post_id referencing any course, lesson, or quiz. The handler then creates a private message addressed to that post's author, bypassing the enrollment checks enforced by the newer REST send-message controller.
Critical Impact
Any authenticated WordPress user, including unprivileged Subscribers, can send private messages to course, lesson, or quiz authors without being enrolled, enabling unauthorized communication and potential social engineering against instructors.
Affected Products
- Sensei LMS WordPress plugin versions prior to 4.26.4
- WordPress sites using the legacy save_new_message handler
- Learning management deployments relying on Sensei LMS enrollment-based messaging
Discovery Timeline
- 2026-10-19 - CVE-2026-112329 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-112329
Vulnerability Analysis
The Sensei LMS plugin exposes two paths for creating private messages between users and course authors. The newer REST send-message controller validates that the requesting user is enrolled in the referenced course before accepting the message. The legacy save_new_message handler, registered on the WordPress init action, performs only a nonce check. It does not validate enrollment status or confirm that the submitted post_id corresponds to a Sensei-managed course, lesson, or quiz post type.
Because the init hook fires on every request, any authenticated session can reach the handler. An attacker with a Subscriber account can forge a submission referencing any arbitrary post_id and cause the plugin to create a private message addressed to that post's author. The access control gap stems from reliance on a nonce as the sole trust boundary.
Root Cause
The root cause is a missing authorization check [CWE-862] in the legacy handler. Nonces mitigate cross-site request forgery but do not enforce authorization. The code path omits the enrollment validation and post-type restriction present in the REST controller, leaving the handler broadly accessible.
Attack Vector
Exploitation requires an authenticated WordPress session with any role, including Subscriber. The attacker submits a crafted request to the init-hooked endpoint with a valid nonce and an arbitrary post_id targeting any course, lesson, or quiz. The plugin creates a private message to the post author without validating enrollment. No user interaction from the victim is required. See the VulnCheck Advisory on Sensei LMS for additional technical details.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-112329
Indicators of Compromise
- Private messages created by Subscriber-role accounts that have no enrollment record for the referenced course, lesson, or quiz.
- Unexpected spikes in Sensei LMS message post types authored by low-privilege accounts.
- Requests to WordPress endpoints during the init action carrying save_new_message parameters from unenrolled users.
Detection Strategies
- Audit the wp_posts table for Sensei message post types correlated against the sensei_user_courses enrollment records to identify messages created without enrollment.
- Review web server access logs for POST requests containing save_new_message fields originating from accounts with the Subscriber role.
- Compare message creation events against the active plugin version to confirm vulnerable installations below 4.26.4.
Monitoring Recommendations
- Enable WordPress audit logging for post creation events tied to Sensei message post types.
- Alert on repeated message creation activity from a single low-privilege account across multiple course authors.
- Track plugin version inventory across WordPress fleets to flag Sensei LMS installations below 4.26.4.
How to Mitigate CVE-2026-112329
Immediate Actions Required
- Upgrade Sensei LMS to version 4.26.4 or later on all WordPress sites.
- Review existing private messages created by Subscriber-role accounts and remove unauthorized entries.
- Restrict new user registration to trusted sources until patching is complete.
Patch Information
The vendor addressed the issue in Sensei LMS 4.26.4 by adding enrollment and post-type validation to the legacy save_new_message handler. Refer to the Sensei LMS Release Notes for upgrade details and version history.
Workarounds
- Temporarily disable the Sensei LMS plugin on sites that cannot be upgraded immediately.
- Block unauthenticated and Subscriber-level POST requests targeting Sensei messaging parameters at the web application firewall.
- Restrict the Subscriber role from accessing the init-hooked messaging endpoint using an access control plugin or custom capability check.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

