Moodle 4.5.16 Security Vulnerabilities: What Each Advisory Means for Your LMS
SQL injection, IDOR across courses, and XSS in SCORM: The 13 Advisories from 11/20/2026 Explained for LMS Administrators.
by Cleverson Gouvêa

Moodle 4.5.16 and 5.3.1 security vulnerabilities were made public on November 20, 2026, eight days after the versions that fix them were released. There are 13 advisories, from MSA-26-0046 to MSA-26-0058, and almost all follow the same pattern: someone already logged into the LMS can view or modify content they shouldn't have access to. In this article, I explain what each vulnerability allows, who is exposed, what to prioritize for correction, and how to confirm your site is patched.
Summary
The 13 advisories (MSA-26-0046 to 0058) are patched in 5.3.1, 5.2.5, 5.1.9, and 4.5.16, released on 11/12/2026. Any earlier version is exposed.
There are 10 vulnerabilities classified as Serious and 3 as Minor. None work without a login: the risk stems from a compromised instructor, student, or stolen account.
The most dangerous: SQL injection in the external database enrollment plugin (MSA-26-0049), arbitrary file read in Blackboard question import (MSA-26-0047), and stored XSS in the SCORM objectives report (MSA-26-0051).
Seven advisories are IDOR: an instructor in one course can edit activities, Lesson pages, Feedback templates, or forum discussions from another course.
Version 5.0.12 does not fix any of this: security support for the 5.0 branch ended on 10/05/2026. Next round expected: 12/07/2026 (5.3.2 and 4.5.17).
If you haven't updated yet, the full procedure is in the guide Moodle 5.3.1: How to Apply the Update Without Downtime for Your LMS. I won't repeat the step-by-step instructions here. This article provides the detailed explanation that was promised there.
What Was Disclosed on November 20
Moodle follows a fixed rule: the patched version is released first, followed by the advisories (MSA, Moodle Security Announcement) about a week later. The versions arrived on 11/12 and the advisories were published on moodle.org/security on 11/20.
Each advisory includes a description, severity (Serious or Minor), affected and patched versions, CVE, and the link to the fix commit on GitHub. This last item changes the game: with the public diff, anyone can see which check was missing. Exploiting these becomes much easier than it was on the 12th.
The list of Moodle 4.5.16 security vulnerabilities doesn't end at 0058. The 4.5.16 release notes extend to MSA-26-0062. Advisories 0059 to 0062 address the quiz module (sections, overrides, random question, and single view report) and are patched in the same versions; 0062 only affects 5.1 and 4.5.
And an alert outside the core: on 11/10, Moodle HQ warned about a critical vulnerability in the third-party plugin Configurable Reports (block_configurable_reports). Update the plugin or disable it; this fix is not included with 4.5.16.
Moodle 4.5.16 and 5.3.1 Security Vulnerabilities in a Table
Before reading the table, a point that applies to all rows: the affected and patched versions are the same across all 13 advisories. Affected: 5.3, 5.2 to 5.2.4, 5.1 to 5.1.8, 4.5 to 4.5.15, and earlier unsupported versions. Patched: 5.3.1, 5.2.5, 5.1.9, and 4.5.16.
AdvisoryLocationWhat it AllowsWho Needs to Be Logged InRiskCVEMSA-26-0046Grade feedback web serviceView grade feedback and profile data of students outside their groupInstructor without editing permissionsMinorCVE-2026-133059MSA-26-0047Blackboard question import formatRead arbitrary filesAnyone who can import questionsSeriousCVE-2026-133060MSA-26-0048Grade item web serviceView the names of all grade items, including hidden onesStudentMinorCVE-2026-133061MSA-26-0049External database enrollment (enrol_database)SQL injection in the external enrollment databaseInstructor with editing permissions, with the plugin activeSeriousCVE-2026-133062MSA-26-0050Activity editingAlter activities in other coursesInstructorSeriousCVE-2026-133063MSA-26-0051SCORM objectives reportStored XSSNot detailed in the advisorySeriousCVE-2026-133064MSA-26-0052Quiz question bankView questions without permission and instantiate arbitrary classesLogged-in userSeriousCVE-2026-133065MSA-26-0053Feedback activity templatesView, use, and delete templates from other coursesInstructorSeriousCVE-2026-133066MSA-26-0054Badge alignmentsView and edit badge alignments belonging to othersAnyone who manages badgesSeriousCVE-2026-133067MSA-26-0055GlossaryView approved entries from glossaries in other coursesLogged-in userMinorCVE-2026-133068MSA-26-0056Forum locking and subscription web servicesView discussion data from other courses and lock themLogged-in user / InstructorSeriousCVE-2026-133069MSA-26-0057Wiki page versionsView and copy content from wikis in other coursesLogged-in userSeriousCVE-2026-133070MSA-26-0058Lesson page editingView and move Lesson pages from other courses into your ownInstructorSeriousCVE-2026-133071
Nine of the thirteen were reported by the same researcher, Vincent Schneider. This tells a story: someone systematically scanned Moodle's access checks module by module. When an audit uncovers nine similar vulnerabilities, it's reasonable to assume others are looking in the same areas.
IDOR: When an Instructor in One Course Accesses a Neighboring Course
IDOR (Insecure Direct Object Reference) is a vulnerability where the system trusts the object ID provided in the request. An instructor is editing activity 1,200 in their course. They change the number to 1,201, which belongs to another course, and Moodle accepts it because it checked if they can edit activities, but not which activity.
Seven of the Moodle 4.5.16 security vulnerabilities follow this pattern:
MSA-26-0050 (Activity editing): the most severe in the group. An instructor can alter activities in courses they don't have access to: due dates, maximum grades, quiz availability.
MSA-26-0058 (Lesson): an instructor views Lesson pages from other courses and moves them into their own Lesson. This is both a data leak and potential content loss.
MSA-26-0053 (Feedback templates): allows viewing, using, and deleting templates from other courses. In an institution that uses Feedback for institutional evaluation, this could delete the standard questionnaire used by the accreditation body.
MSA-26-0056 (Forum): exposes discussion information from other courses and allows the instructor to lock them.
MSA-26-0057 (Wiki): reads versions of wiki pages from others and copies the content to their own wiki.
MSA-26-0054 (Badges): anyone who manages badges can view and edit badge alignments that are not their own.
MSA-26-0055 (Glossary): approved entries from other courses become visible. It's Minor, but still a data leak.
Who Should Be Most Concerned About IDOR
In a small school where the same instructors teach all courses, the vulnerability has less impact. The dangerous scenario is a shared Moodle instance: multiple departments, corporate clients, partners, or third-party tutors on the same installation. There, security relies on the premise that an instructor from Company A cannot see Company B's content. These vulnerabilities break that premise.
Also concerning is a stolen account: if an instructor's password is leaked via phishing, a regular instructor account can then access the entire site.
Web Services Without Access Checks
A web service is the gateway through which the Moodle app, the dynamic screens of the LMS itself, and external integrations communicate with the server. When such a function forgets to check permissions, the interface might hide the data, but it remains available to anyone calling the function directly. Hiding a button does not close any of the Moodle 4.5.16 security vulnerabilities in this group.
MSA-26-0046: Grade feedback outside the group
Missing group and enrollment checks in a grade feedback web service. An instructor without editing permissions (the tutor in most institutions) could access grade feedback and profile data of users they shouldn't see. In a course with groups by campus or branch, a tutor from Campus A could read feedback given to students from Campus B.
The advisory classifies this as Minor. From a privacy standpoint (e.g., under CCPA or state privacy laws), this shouldn't be treated as a minor detail: grades and instructor comments are personal student data. Minor, here, means limited technical impact, not a license to delay action.
MSA-26-0048: The student who sees hidden grade items
Here, the actor is the student. The function returned the names of all grade items in the course, including hidden ones, such as a “Makeup Exam” created weeks in advance. The student doesn't see the grade, but they see the plan.
MSA-26-0052: Quiz question bank
The most serious in this group. Insufficient checks in a quiz question bank function allowed viewing questions from unauthorized banks and the instantiation of arbitrary classes. For those administering online exams, a leaked question bank means rebuilding it.
The Three Vulnerabilities Requiring Immediate Correction
If I had to choose where to look first, it would be these three: they are the Moodle 4.5.16 security vulnerabilities with the highest potential for technical damage.
MSA-26-0049: SQL injection in the external database enrollment plugin
The enrol_database plugin synchronizes enrollments from an external database, typically the academic information system. The advisory points to an SQL injection risk that affects this external database. There are two conditions: the plugin must be active, and the attacker needs instructor access with editing permissions.
If you don't use enrol_database, this item doesn't apply. If you do, it goes to the top: the external database is usually the academic information system, containing registration and financial data for all students.
MSA-26-0047: File reading via Blackboard import
The Blackboard question import format allowed reading arbitrary files from the server. This requires the ability to import questions into a question bank, which instructors with editing permissions typically have.
Reading a file on a Moodle server means, in the worst-case scenario, reading config.php, which stores the database password. With this, the attacker no longer depends on Moodle.
MSA-26-0051: Stored XSS in the SCORM objectives report
SCORM objective identifiers appeared in the report without proper sanitization. This is stored XSS: the code is saved and runs in the browser of anyone who opens the report, typically an instructor or administrator. With an administrator's session, the attacker can achieve almost anything.
The advisory does not detail who can inject the malicious identifier. Since objectives come from the SCORM package and tracking data, treat any LMS using SCORM as urgent, especially if it accepts packages from various vendors or allows any instructor to upload packages.
Who Is Affected, Version by Version
Any Moodle instance not on 5.3.1, 5.2.5, 5.1.9, or 4.5.16 is exposed to the 13 vulnerabilities. In other words, the Moodle 4.5.16 security vulnerabilities apply to all branches, not just 4.5. The support table for each branch is in the 5.3.1 guide and on moodledev.io.
The case that concerns me most is 5.0. Version 5.0.12 was released on the same day, and many people installed it believing they were covered. They are not: its release notes state that no security fixes were applied because security support for that branch ended on 10/05/2026. Since 11/20, anyone on 5.0 (or 4.4 and earlier) has 13 documented vulnerabilities, with the fix commit publicly available, and no official version that closes them.
Those on 4.5 LTS have the most comfortable situation among older versions: with 4.5.16 applied, the vulnerabilities are closed, and the branch receives security fixes until 10/04/2027.
How to Prioritize Moodle 4.5.16 Security Vulnerabilities in Your LMS
Updating resolves the Moodle 4.5.16 security vulnerabilities at once. Prioritizing serves another purpose: deciding how long you can wait and what to monitor until the update window arrives. Answer five questions:
Is enrol_database active? If so, urgency is maximum.
Does your LMS serve more than one organization? The seven IDORs become data leaks between clients, with contractual consequences.
Is SCORM in use, and can instructors import questions? If so, 0047 and 0051 count as truly Serious.
Are online exams with sensitive question banks in use? 0052 puts the question bank at risk.
Are you on 5.0 or earlier? Then the problem shifts from prioritizing a patch to planning a migration.
Mitigations for the Days Until Your Update Window
If the update needs to wait a few days (e.g., due to an ongoing exam), reduce the attack surface:
Deactivate enrol_database if synchronization can be paused for a few days. Warning: with the plugin disabled, new enrollments from the academic information system will not be processed. Coordinate with your registrar's office.
Restrict who can import questions and upload SCORM packages by reviewing custom roles.
Review instructor accounts: deactivate accounts of former employees and require password changes where suspicion exists.
Update or deactivate Configurable Reports, which has its own alert.
What doesn't work against Moodle 4.5.16 IDOR-type security vulnerabilities: relying on a WAF. An application firewall blocks known patterns, like a typical SQL injection string, but it doesn't understand the business rule “this instructor cannot edit that course”. For IDORs, the malicious request is identical to a legitimate one, just with a different ID.
How to Verify Your Site Is Patched
“I updated” and “it's patched” are different statements. To truly close the Moodle 4.5.16 security vulnerabilities, check the version, code, instances, and plugins. It's common for production to be on the new version while staging, accessible on the internet with a copy of the real database, remains on the old one.
1. The Version Displayed in the Dashboard
Under Site administration > Notifications, the footer shows the running version. You need to see 4.5.16, 5.1.9, 5.2.5, or 5.3.1, or a higher version of the same branch. Any lower number means the Moodle 4.5.16 security vulnerabilities remain open on your site.
2. The Version in the Code, via Terminal
In the code root, the variable $release in the version.php file indicates the actually installed version:
grep -E '^\$release' version.php
If the code comes from the official Git repository, git describe --tags should point to the patched version's tag (for example, v4.5.16). If your Moodle has core customizations, also confirm that they haven't reverted any patched sections.
3. All Instances, Not Just the Main One
The Moodle 4.5.16 security vulnerabilities remain applicable to any forgotten copy. List everything running Moodle with real data: production, staging, replicas, old containers, an LMS for an event that no one shut down. Each must be patched or taken offline.
4. Third-Party Plugins
Under Site administration > Plugins > Plugins overview, filter for additional plugins. Check Configurable Reports and any abandoned plugins.
5. The Traces, If You Updated Late
If your site was exposed to the Moodle 4.5.16 security vulnerabilities after 11/20, it's worth checking the logs. Under Reports > Logs, look for course module update events performed by instructors in courses they are not enrolled in, as well as deletions of Feedback templates and moved Lesson pages. For 0049, review the logs of the external enrollment database. The Moodle server security checklist after PHP2Shell covers the server-side aspect of this investigation.
Remember also that PHP had its own round of fixes on 11/19. A Moodle updated on top of a vulnerable PHP remains vulnerable. I detailed this in PHP security update: November's critical vulnerabilities.
How Agathas Web Addresses This
With Agathas Web's managed Moodle hosting, addressing Moodle 4.5.16 security vulnerabilities or the next round doesn't depend on someone on your team reading an English advisory. What's included:
Advisory Triage. When Moodle publishes MSAs, we cross-reference each advisory with what your LMS actually uses (enrol_database, SCORM, multiple organizations), and you receive a prioritized report in English.
Validated Staging Updates on Professional and Enterprise plans, with a production-mirrored environment, before touching the live LMS.
Coordinated Maintenance Window outside of class and assessment hours, with full daily backups, binlog every 15 minutes, and monthly tested restoration.
Comprehensive Instance and Plugin Checks, including alerts for third-party plugins like Configurable Reports.
Dedicated Moodle Stack, with Cloudflare WAF, rate limiting on critical routes, and 24/7 monitoring with alerts to the technical team's WhatsApp.
In practice, you remain the owner of your LMS and pedagogical decisions, while the security pipeline is handled by us. Support is provided by the team that configures the server, with an SLA of up to 15 minutes response time for critical incidents.
To get started, request a free diagnostic on our Moodle hosting page. Within 3 business days, we'll identify your current version, plugins, and exposure. If your LMS is on 5.0 or an older version, the diagnostic will include a migration plan.
Conclusion: Patch Now and Mark 12/07 on Your Calendar
The Moodle 4.5.16 and 5.3.1 security vulnerabilities don't bring down your LMS from the outside in. They allow those already inside to go too far: the tutor who reads a neighboring campus's content, the instructor who alters another client's course, the stolen account that accesses the academic information system. Since 11/20, the blueprint for each is publicly available.
The roadmap against Moodle 4.5.16 security vulnerabilities is straightforward. Confirm the version on all instances, prioritize enrol_database, SCORM, and question import first, and don't rely on 5.0.12. Then, mark 12/07/2026 on your calendar, the expected release date for 5.3.2 and 4.5.17.
If your team lacks the resources to keep up with this every release cycle, managed Moodle hosting exists to take this task off your plate.
Related posts

Moodle Workplace 5.3: What's New and What It Means for Enterprise L&D
Multi-tenant accounts, AI queries capped at 500 rows, and a revamped catalog: what Workplace 5.3 delivers and how to achieve the same results without premium licensing.

Moodle Configurable Reports: Critical Vulnerabilities and How to Respond
Two CVEs hit Moodle's most widely used custom reporting plugin. Check if your LMS is exposed and how to patch without breaking administrative reports.

Coassemble Moodle: Is the Certified Integration Worth It?
Coassemble is now a Moodle Certified Integration. We evaluate pricing, H5P vs. SCORM workflows, system requirements, and CCPA privacy compliance.