CVE-2026-116757 in Tutor Lms Plugin
Summary
by MITRE • 11/21/2026
The Tutor LMS – eLearning and online course solution plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the '_tutor_profile_bio' parameter in all versions up to, and including, 4.2.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The injected anchor payload uses a full-viewport invisible overlay (position:fixed; width:100vw; height:100vh; opacity:0) so that any click on the public profile page triggers the tutor-copy-text handler, which passes a browser-decoded data-text value to tutor_toast() where it is parsed as live HTML by jQuery.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Analysis
by VulDB Data Team • 11/21/2026
The Tutor LMS plugin for WordPress contains a critical stored cross-site scripting vulnerability affecting all versions up to and including 4.2.0. This flaw stems from insufficient input sanitization and output escaping mechanisms within the application code, specifically targeting the _tutor_profile_bio parameter used in user profile management features. The security deficiency allows authenticated attackers with subscriber-level access or higher privileges to inject arbitrary web scripts into stored data fields that are subsequently rendered on public-facing pages without proper validation.
The technical execution of this vulnerability relies on a sophisticated payload design intended to bypass standard detection methods and maximize impact upon interaction by legitimate users. Attackers can craft an anchor element utilizing CSS properties such as position fixed, width one hundred viewport widths, height one hundred viewport heights, and opacity zero to create a full-viewport invisible overlay. This technique effectively masks the malicious input from visual inspection while ensuring it covers the entire user interface area of the public profile page.
When any visitor accesses the compromised profile page, their interaction with the visible surface triggers the tutor-copy-text handler embedded in the frontend JavaScript logic. This event listener captures data attributes associated with the injected anchor element and passes a browser-decoded value to the tutor_toast function. Crucially, this function processes its input as live HTML using jQuery rather than treating it as plain text or safely escaped content. Consequently, any script tags contained within the decoded attribute are executed immediately in the context of the victim's session.
This vulnerability falls under CWE-79, which classifies improper neutralization of input during web page generation known as cross-site scripting. The attack vector aligns with MITRE ATT&CK technique T1059, specifically command and script interpretation through browser-based execution environments like JavaScript. Because the payload is stored server-side within user profile data, it constitutes a persistent threat that affects every subsequent visitor to the affected profiles rather than just the attacker themselves.
The operational impact of this vulnerability extends beyond simple defacement or alert boxes. Attackers can leverage the executed scripts to perform session hijacking by stealing authentication cookies and tokens transmitted during active sessions. This capability enables unauthorized access to user accounts, potentially escalating privileges if combined with other vulnerabilities or social engineering tactics. Furthermore, attackers may redirect users to malicious phishing sites designed to harvest credentials or distribute malware under the guise of legitimate platform interactions.
Mitigation strategies must prioritize immediate remediation through software updates and defensive coding practices. Administrators should upgrade Tutor LMS to version 4.2.1 or later where these sanitization issues have been addressed by the development team. In environments where upgrading is not immediately feasible, implementing a Web Application Firewall with rules capable of detecting and blocking script injection patterns in profile bio fields can provide temporary protection. Additionally, enforcing strict Content Security Policy headers that restrict inline script execution can significantly reduce the success rate of such attacks even if input validation fails.
Long-term security improvements require adopting secure coding standards that mandate output encoding for all dynamic content rendered to browsers. Developers should utilize context-aware escaping functions provided by WordPress core APIs rather than relying on generic sanitization routines. Regular code audits focusing on data flow from user inputs through storage mechanisms and into final HTML generation processes will help identify similar weaknesses before they can be exploited in production environments.