Lesson completion business logic bypass in Koollab LMS SCORM commit endpoint
CVE-2026-63242 is a business logic vulnerability in Koollab LMS 5.3.2 that allows an authenticated learner to mark a lesson as completed through the SCORM commit endpoint without actually viewing or completing the lesson material. The flaw stems from insufficient server-side enforcement of the intended training workflow and trust in client-submitted progress state, enabling unauthorized modification of lesson completion records.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows a learner to falsify training progress and completion status. This compromises the integrity of learning records, compliance tracking, and assessment of whether required material was actually consumed. The primary impact is on data integrity and trustworthiness of completion records rather than code execution or privilege escalation.
If you can’t patch tonight, do this now.
Where immediate code remediation is not possible, monitor for anomalous completion events that occur without corresponding lesson access patterns, review and reconcile suspicious training records, and apply compensating controls around compliance-sensitive course completion workflows. Restricting unnecessary learner capabilities and adding server-side validation of SCORM state transitions can reduce exposure.
Patch, then assume compromise.
Vendor fixes were rolled out across Koollab LMS cloud-hosted instances on 2026-04-26. Remediation requires enforcing lesson progression and completion rules on the server side within the SCORM commit handling logic, ensuring completion status cannot be set unless prerequisite lesson-viewing or completion conditions have been verifiably satisfied.
No public exploits tracked yet. Mallory keeps watching.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.