CVE-2026-119098 · Package
NO FIX YET
The LifterLMS WordPress plugin does not sanitize the 'answer[]' quiz parameter, so a student can store a script that runs later. When an administrator opens the attempt during grading ('Start a Review'), the script runs in their browser session.
first public Nov 7, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the LifterLMS plugin for WordPress at version 10.3.2 or earlier, where students take quizzes with Content-type questions. The risk lands on administrators and graders who open student attempts with 'Start a Review'. Sites without LifterLMS, or on a newer version, can skip it.
Not affected if newer-version, no-content-type-quiz-questions, plugin-not-installed
Who cares elearning, lifterlms, wordpress
10.3.2).lifterlms directory under wp-content/plugins/ and read its version header.No fix yet, per the sources.
The LifterLMS – WP LMS for eLearning, Online Courses, & Quizzes plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'answer[]' parameter in all versions up to, and including, 10.3.2 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. Exploitation requires the attacker to be enrolled as a student in a course containing a Content-type quiz question; the injected payload executes in the administrator's browser session during the normal grading workflow when 'Start a Review' is clicked on the affected attempt.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.