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-93681 Overview
CVE-2026-93681 is a Stored Cross-Site Scripting [CWE-79] vulnerability in the Tutor LMS – eLearning and online course solution plugin for WordPress. The flaw affects all versions up to and including 4.1.0 and stems from insufficient input sanitization and output escaping of the display_name parameter. Authenticated users with subscriber-level access or higher can inject arbitrary JavaScript that executes when administrators view the affected admin page. Exploitation requires a Legal Consent record to exist for the attacker's user account, which causes the View Logs button to render in the Consent Logs column of wp-admin/users.php.
Critical Impact
Low-privileged WordPress users can inject persistent JavaScript that executes in an administrator's browser session, enabling account takeover or privilege escalation on sites running Tutor LMS 4.1.0 or earlier.
Affected Products
- Tutor LMS – eLearning and online course solution plugin for WordPress
- All versions up to and including 4.1.0
- WordPress sites with the GDPR Consent feature in use
Discovery Timeline
- 2026-10-16 - CVE-2026-93681 published to NVD
- 2026-10-16 - Last updated in NVD database
Technical Details for CVE-2026-93681
Vulnerability Analysis
The vulnerability resides in the GDPR consent logging workflow of the Tutor LMS plugin. When a user record contains a Legal Consent entry, a View Logs control is rendered in the Consent Logs column of the WordPress users administration screen. The plugin passes the user's display_name value into this rendered output without applying adequate sanitization on input or escaping on output. Any script payload stored in display_name therefore executes in the context of the viewing user, typically an administrator reviewing consent records.
Because the payload is stored server-side, the attack is persistent. Each time an authenticated administrator loads wp-admin/users.php, the injected script runs with the privileges of that session. Attackers can use this to create new administrator accounts, exfiltrate nonces, modify plugin settings, or pivot further into the WordPress environment.
Root Cause
The root cause is improper neutralization of input during web page generation. Code paths in the plugin's GDPR/Controllers/UserConsent.php and classes/Student.php files render the display_name field directly into the admin interface. Standard WordPress escaping helpers such as esc_html() or esc_attr() were not applied to the output, allowing stored HTML and JavaScript to reach the DOM intact.
Attack Vector
An authenticated subscriber-level account updates its profile display_name with a crafted script payload. The attacker then triggers the plugin's Legal Consent flow so a consent record is created against their user ID. When an administrator subsequently opens the WordPress Users screen, the Consent Logs column renders the attacker's display_name, and the stored script executes in the administrator's browser session.
See the Wordfence Vulnerability Analysis and the vendor-side WordPress Tutor Changeset Review for technical details.
Detection Methods for CVE-2026-93681
Indicators of Compromise
- WordPress user accounts whose display_name field contains HTML tags, <script> elements, or JavaScript event handlers such as onerror= or onload=.
- Unexpected administrator accounts created shortly after an administrator viewed wp-admin/users.php on a site running Tutor LMS 4.1.0 or earlier.
- Outbound HTTP requests from administrator browser sessions to attacker-controlled domains following access to the Users screen.
Detection Strategies
- Query the wp_users table for display_name values containing <, >, or javascript: substrings and review any matches.
- Inspect WordPress audit logs for subscriber-level accounts updating their profile display_name followed by GDPR consent record creation.
- Monitor web server access logs for POST requests to Tutor LMS GDPR consent endpoints originating from low-privilege sessions.
Monitoring Recommendations
- Enable WordPress security plugin logging for user profile changes and administrator session actions.
- Alert on new administrator role assignments or plugin configuration changes immediately following admin visits to the Users screen.
- Deploy Content Security Policy (CSP) headers to constrain inline script execution in the WordPress admin interface and surface violations.
How to Mitigate CVE-2026-93681
Immediate Actions Required
- Update the Tutor LMS plugin to a version later than 4.1.0 that includes the fix referenced in the vendor changeset.
- Audit all WordPress user accounts for suspicious display_name values and reset or sanitize any that contain markup.
- Review administrator accounts and recent role changes for signs of unauthorized privilege escalation.
Patch Information
The fix is tracked in the vendor repository and visible in the WordPress Tutor Changeset Review. Site administrators should upgrade Tutor LMS to the patched release that supersedes version 4.1.0. See also the referenced source files UserConsent.php and Student.php for the vulnerable code paths.
Workarounds
- Temporarily disable the Tutor LMS GDPR Consent feature until the plugin is updated.
- Restrict new user registration or require manual approval to prevent untrusted subscriber-level accounts from being created.
- Apply a Web Application Firewall rule that blocks HTML and script characters in profile update requests targeting the display_name field.
# Example WP-CLI check for suspicious display_name values
wp db query "SELECT ID, user_login, display_name FROM wp_users \
WHERE display_name REGEXP '<|>|script|onerror|onload|javascript:';"
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

