Summary
CVE-2026-19092 is a critical, unauthenticated vulnerability in the Tutor LMS WordPress plugin caused by improper handling of request data during template rendering, which allows attackers to invoke arbitrary zero-argument PHP functions and retrieve their output. The flaw affects Tutor LMS versions 2.1.3 through versions prior to 4.0.6 and carries a CVSS v3.1 base score of 9.8 (Critical), reflecting full compromise of confidentiality, integrity, and availability without authentication or user interaction.
Technical details
- Root cause: The plugin fails to prevent request data (e.g., query/POST parameters) from overwriting internal variables while rendering templates, a form of PHP variable/template variable shadowing.
- Trigger conditions: An attacker sends a crafted, unauthenticated HTTP request to a site running the vulnerable plugin; no login or user interaction is required.
- Attack vector: Network-based (AV:N), low attack complexity (AC:L), no privileges (PR:N), no user interaction (UI:N).
- Impact: Successful exploitation lets an attacker invoke arbitrary zero-argument PHP functions and read their return values, which can be leveraged to destroy user sessions, delete WordPress options, or drop database tables — resulting in high impact to confidentiality, integrity, and availability.
Affected software
- Tutor LMS WordPress plugin, versions 2.1.3 up to (but not including) 4.0.6
Severity
- CVSS v3.1 Base Score: 9.8 (Critical)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: Upgrade Tutor LMS to version 4.0.6 or later, where the template variable overwrite issue has been fixed.
- If immediate patching is not possible: Restrict or monitor unauthenticated access to the plugin’s front-end template rendering endpoints, and consider temporarily deactivating the plugin until the update can be applied. A web application firewall may help detect anomalous request parameters targeting template rendering paths, though this is not a substitute for patching.
How IONIX identifies potentially affected assets
IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.
- Raw response body:
/wp-content/plugins/tutor/

