CVE-2026-18439

The Tutor LMS plugin for WordPress up to version 4.0.1 is vulnerable to generic SQL Injection via the 'coupon_code' parameter due to insufficient escaping and lack of proper query preparation. Authenticated attackers with administrator-level access or higher can append additional SQL queries to existing ones, potentially extracting sensitive information from the database.

The Tutor LMS WordPress plugin before version 4.0.6 does not prevent request data from overwriting internal variables while rendering templates, allowing unauthenticated users to invoke arbitrary zero-argument PHP functions and receive their output.

The Tutor LMS plugin for WordPress (versions up to and including 4.0.8) is vulnerable to Insecure Direct Object Reference (IDOR) via the 'student_id' parameter. Missing validation on a user-controlled key allows authenticated attackers with subscriber-level access and above to disclose the email address and Tutor profile phone number of arbitrary WordPress users, including Administrators, by iterating over user IDs.

The Tutor LMS plugin for WordPress (versions up to and including 4.0.8) is vulnerable to Reflected Cross-Site Scripting via the 'search' parameter due to insufficient input sanitization and output escaping. This allows unauthenticated attackers to inject arbitrary web scripts into pages that execute if they can trick a user into clicking a link.

The Tutor LMS plugin for WordPress (versions up to and including 4.0.8) is vulnerable to authorization bypass due to improper verification that a user is authorized to perform an action. This allows authenticated attackers with subscriber-level access and above to permanently delete arbitrary WordPress posts — including pages, courses, quizzes, and WooCommerce products — via wp_delete_post( $id, true ). The exploit chain requires triggering the profile-photo upload flow, creating a Tutor topic reparented to that attachment, then invoking the lesson deletion handler against any target post ID.

The Tutor LMS WordPress plugin before 4.0.8 does not check that a user has access to a course before returning its lesson discussion content. This allows any authenticated user, such as a subscriber, to read comments from courses they are not enrolled in, including comments awaiting moderation.

The Tutor LMS WordPress plugin before 4.0.8 does not correctly determine whether an incoming request is addressed to its own REST API, and does not enforce the permission recorded against an API credential. This allows the holder of a read-only key to act as the administrator account that issued it.

The Tutor LMS plugin for WordPress (versions up to and including 4.0.7) is vulnerable to PHP Object Injection via the `withdraw_method_field` parameter of the `tutor_save_withdraw_account` AJAX handler. The handler lacks capability or role checks, relying solely on a nonce, and passes attacker-supplied values through `esc_sql()`, causing serialized string length mismatches that allow injection of an arbitrary serialized object stream. An authenticated attacker with subscriber-level access or above can achieve remote code execution via the `GuzzleHttp\Cookie\FileCookieJar` POP chain, with an unauthenticated pathway when user registration is enabled.

The Tutor LMS – eLearning and online course solution plugin for WordPress is vulnerable to Remote Code Execution limited to zero-argument function invocation in all versions up to, and including, 4.0.5 via the tutor_course_filter_ajax AJAX action. Missing authorization combined with unsanitized array keys passed to extract() inside tutor_load_template() allow attacker-controlled POST data to overwrite local variables and invoke arbitrary zero-argument PHP functions.

The Tutor LMS WordPress plugin before version 4.0.6 does not validate values used to build a database query and does not restrict which template file a request may load, allowing unauthenticated users to inject SQL and read question and answer content from courses that are not publicly available. The injected text reaches the query as grammar rather than as data, and on the database engines tested it does not yield extraction of arbitrary data, so the confidentiality impact is the disclosed course content rather than the database at large.