Moodle 4.5.16 Security Flaws: Breakdown of All 13 Advisories
SQL injection, cross-course IDOR, and SCORM XSS: all 13 November security bulletins explained for UK VLE administrators.
by Cleverson Gouvêa

The security vulnerabilities in Moodle 4.5.16 and 5.3.1 were made public on 20 November 2026, eight days after the patched releases dropped. There are 13 advisories in total, spanning MSA-26-0046 to MSA-26-0058, and virtually all share a common threat model: an authenticated user inside the VLE gaining unauthorised access to view or modify data outside their remit. Below, we break down what each flaw allows, who is exposed, what to patch first, and how to verify your deployment is secure.
TL;DR
- All 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 12/11/2026. Any earlier release is exposed.
- The batch includes 10 vulnerabilities rated Serious and 3 rated Minor. None can be exploited without an active session: the attack vector stems from students, course tutors, or compromised credentials.
- The highest-risk flaws: SQL injection in the external database enrolment plugin (MSA-26-0049), arbitrary file read during Blackboard question imports (MSA-26-0047), and stored XSS in SCORM objective reporting (MSA-26-0051).
- Seven advisories represent IDOR vulnerabilities: a tutor in one course can alter activities, Lesson pages, Feedback templates, or forum discussions belonging to another course.
- Moodle 5.0.12 addresses none of these issues: security support for 5.0 ceased on 05/10/2026. The next scheduled minor release window is 07/12/2026 (5.3.2 and 4.5.17).
If you have not updated yet, the full zero-downtime workflow is covered in our operational guide, Moodle 5.3.1: Upgrading your VLE without downtime. Here, we delve straight into the technical breakdown of the advisories.
What was disclosed on 20 November
Moodle operates on a responsible disclosure schedule: security releases ship first, followed by public security advisories (MSAs) roughly one week later. The updated packages arrived on 12/11, and the formal notices were published at moodle.org/security on 20/11.
Each advisory outlines the vulnerability description, severity rating (Serious or Minor), affected and patched branches, CVE identifier, and the direct link to the security commit on GitHub. The public commit diff changes the operational threat level immediately: anyone can inspect exactly which capability checks were missing, making automated exploitation significantly easier than it was on release day.
The scope of Moodle 4.5.16 fixes does not stop at advisory 0058. The official 4.5.16 release notes extend to MSA-26-0062. Advisories 0059 through 0062 cover Quiz sub-systems (sections, user overrides, random questions, and the single view report) and were addressed simultaneously; note that 0062 affects only 5.1 and 4.5.
There is also an urgent third-party notice: on 10/11, Moodle HQ flagged a critical vulnerability in the popular community plugin Configurable Reports (block_configurable_reports). You must upgrade or disable this plugin independently; core Moodle upgrades will not patch it.
Moodle 4.5.16 and 5.3.1 vulnerabilities at a glance
Across all 13 core advisories, the impacted branches remain uniform: versions 5.3, 5.2 through 5.2.4, 5.1 through 5.1.8, 4.5 through 4.5.15, and legacy end-of-life branches are vulnerable. The patched targets are 5.3.1, 5.2.5, 5.1.9, and 4.5.16.
| Advisory | Component | Impact | Required Role | Severity | CVE |
|---|---|---|---|---|---|
| MSA-26-0046 | Grade feedback web service | View grade feedback and profile details of students outside assigned group | Non-editing teacher | Minor | CVE-2026-133059 |
| MSA-26-0047 | Blackboard question import format | Arbitrary local file read | User with question import rights | Serious | CVE-2026-133060 |
| MSA-26-0048 | Grade item web service | View names of all grade items, including hidden assessments | Student | Minor | CVE-2026-133061 |
| MSA-26-0049 | External database enrolment (enrol_database) | SQL injection targeting the external enrolment database | Editing teacher, plugin active | Serious | CVE-2026-133062 |
| MSA-26-0050 | Activity editing interface | Modify activities across other courses | Teacher / Course creator | Serious | CVE-2026-133063 |
| MSA-26-0051 | SCORM objectives report | Stored cross-site scripting (XSS) | Not detailed in advisory | Serious | CVE-2026-133064 |
| MSA-26-0052 | Question bank service | View unauthorised questions and instantiate arbitrary classes | Authenticated user | Serious | CVE-2026-133065 |
| MSA-26-0053 | Feedback activity templates | View, deploy, and delete templates belonging to other courses | Teacher | Serious | CVE-2026-133066 |
| MSA-26-0054 | Badge alignments | View and modify badge alignments configured in other contexts | Badge administrator | Serious | CVE-2026-133067 |
| MSA-26-0055 | Glossary module | Read approved glossary entries from other courses | Authenticated user | Minor | CVE-2026-133068 |
| MSA-26-0056 | Forum lock and subscription web services | Inspect external course discussion metadata and lock threads | Authenticated user / Teacher | Serious | CVE-2026-133069 |
| MSA-26-0057 | Wiki page history | View and clone page revisions from other course wikis | Authenticated user | Serious | CVE-2026-133070 |
| MSA-26-0058 | Lesson page editing | Inspect and relocate Lesson pages from other courses into own module | Teacher | Serious | CVE-2026-133071 |
Nine of the thirteen flaws were credited to a single security researcher, Vincent Schneider. This highlights a concerted audit of Moodle’s access control routines. When a structured audit identifies nine related authorisation gaps, external threat actors will invariably follow the same audit paths.
IDOR: when tutors modify neighbouring courses
An Insecure Direct Object Reference (IDOR) occurs when an application trusts user-supplied object identifiers without validating context ownership. A tutor editing activity ID 1200 in their own course alters the HTTP request parameter to 1201 (belonging to another faculty or client). Because Moodle merely checked whether the user held the general capability to edit activities—without checking which specific course the activity belonged to—the update succeeded.
Seven of the November advisories stem directly from IDOR flaws:
- MSA-26-0050 (Activity editing): The most critical IDOR in the batch. A course tutor can alter parameters in foreign courses: submission deadlines, maximum grade weighting, or quiz availability settings.
- MSA-26-0058 (Lesson): A tutor can view Lesson pages from external courses and move them into their own syllabus, causing immediate data leakage and curriculum corruption simultaneously.
- MSA-26-0053 (Feedback templates): Allows users to view, apply, and permanently delete survey templates across other courses. For UK higher education institutions running institution-wide student satisfaction surveys, an unvetted tutor could wipe central QA templates.
- MSA-26-0056 (Forum): Exposes internal thread metadata from restricted courses and permits arbitrary thread locking.
- MSA-26-0057 (Wiki): Reads historical revisions of other departmental wikis and copies intellectual property directly.
- MSA-26-0054 (Badges): Allows badge managers to inspect and alter badge alignment metadata across unrelated programmes.
- MSA-26-0055 (Glossary): Approved entries from private course glossaries become readable. Though rated Minor, this constitutes an unauthorised cross-tenant information disclosure.
Assessing IDOR exposure across your organisation
In a small single-school setup where teaching staff share curriculum responsibilities across all classes, the operational impact may be minimal. However, in multi-tenant or shared Moodle environments—such as university consortia, corporate apprenticeship providers, NHS trusts, or multi-academy trusts (MATs)—this is critical. Multi-tenancy hinges on strict tenant isolation: an instructor from Partner A must never access records belonging to Partner B. These vulnerabilities break that boundary.
Furthermore, consider credential stuffing and phishing: a single compromised academic staff account grants an attacker lateral reach across the entire instance.
Unauthorised access via Web Services
Web services underpin the Moodle Mobile App, modern dynamic frontend components, and external integrations (such as CRM or analytics pipelines). When a core web service endpoint omits capability checks, hiding buttons in the web UI provides zero defence—any authenticated client can query the API directly.
MSA-26-0046: grade feedback leakage outside group boundaries
This web service omitted strict group and course enrolment validations. A non-editing tutor (often a teaching assistant or external marker) could retrieve assignment feedback and user profile metadata for students in separate cohorts or regional centres.
While Moodle HQ classifies this as Minor due to restricted write impact, under the UK GDPR and Data Protection Act 2018, academic feedback coupled with identifiable personal data constitutes protected student data. An uncontained cross-cohort exposure could trigger internal reporting or Information Commissioner's Office (ICO) scrutiny. It cannot be overlooked.
MSA-26-0048: hidden grade items disclosed to students
Here, the vulnerability is exposed to the student role. The web service returned the names of all gradebook items, including unreleased resit assessments or future exam modules scheduled weeks ahead. While actual scores remain hidden, assessment planning and curriculum roadmaps are leaked.
MSA-26-0052: quiz question bank enumeration and class instantiation
The most acute API failure in this release. Deficient permission checks in question bank routines allowed authenticated users to read raw questions across private categories and trigger arbitrary PHP class instantiation. For institutions running high-stakes online examinations, a compromised question repository compromises the entire assessment cycle.
The three highest-priority vulnerabilities
If your change control board requires phased patching, these three issues pose the highest technical risk to underlying infrastructure.
MSA-26-0049: SQL injection in enrol_database
The enrol_database plugin synchronises student enrolments directly from an external relational database—typically a central Student Record System (SRS) or corporate HR system. The advisory details an authenticated SQL injection flaw impacting that connected database. Two conditions must be met: the plugin must be enabled, and the actor must hold course editing privileges.
If your organisation does not use database enrolment syncs, your risk is zero. If you do, this vulnerability jumps to priority one: your connected database frequently holds sensitive student identifiers, addresses, and finance data.
MSA-26-0047: local file inclusion via Blackboard import
The Blackboard question import parser allowed an attacker to read arbitrary files on the hosting server. Exploitation requires standard question import privileges, which standard editing tutors possess by default.
Arbitrary file reads on a Moodle server can expose config.php, revealing cleartext database credentials and application salts. Once database credentials leak, perimeter controls become obsolete.
MSA-26-0051: stored XSS in SCORM objective tracking
SCORM objective identifiers were rendered in admin reporting screens without rigorous output encoding. Because the payload is persistent (stored XSS), it executes whenever an administrator or lead instructor reviews the module analytics. Hijacking a privileged administrator session grants total control over the Moodle deployment.
Because SCORM tracking strings can originate from third-party vendor packages, any enterprise VLE delivering diverse eLearning content or allowing tutors to upload SCORM packages must treat this fix as urgent.
Branch support status and upgrade paths
Every Moodle installation not running 5.3.1, 5.2.5, 5.1.9, or 4.5.16 remains vulnerable. You can review the long-term support (LTS) lifecycle roadmap in our Moodle 5.3.1 technical guide and on moodledev.io.
The most precarious posture involves Moodle 5.0. Version 5.0.12 was issued simultaneously, prompting some teams to assume they were patched. They are not: the release notes explicitly confirm that zero security patches were backported, as security maintenance for the 5.0 branch formally lapsed on 05/10/2026. Anyone remaining on 5.0, 4.4, or earlier is operating on an unsupported codebase with public proof-of-concept diffs.
Conversely, organisations on 4.5 LTS maintain a stable posture: deploying 4.5.16 remediates all listed CVEs, with dedicated security maintenance continuing through to 04/10/2027.
Prioritising remediation in your environment
Applying the core update resolves all 13 issues in a single maintenance window. However, risk triaging determines how aggressively you must schedule emergency downtime. Ask your infrastructure team these five questions:
- Is enrol_database active? If enabled, patch immediately or isolate the connector.
- Does your VLE host multiple clients, colleges, or distinct business units? The seven IDOR flaws break tenant segregation, creating data breach liabilities under UK GDPR.
- Are tutors uploading SCORM or importing external test banks? If yes, MSA-26-0047 and MSA-26-0051 elevate technical compromise risks.
- Do you run summative online assessments with restricted question banks? MSA-26-0052 invalidates assessment confidentiality.
- Is your instance on Moodle 5.0 or older? If so, this is no longer a patching task; you require an immediate migration plan.
Short-term mitigations ahead of the maintenance window
If you cannot deploy the update immediately (for instance, during an active university exam period), apply these interim controls:
- Temporarily disable enrol_database if batch syncs can pause for 48 hours. Note: new student registrations from your student records system will pause, so coordinate with your registry team.
- Restrict question import and SCORM upload permissions by tightening custom role capabilities.
- Audit dormant tutor accounts: suspend leavers and enforce multi-factor authentication (MFA) across all staff roles.
- Update or deactivate Configurable Reports immediately.
A crucial architecture note: do not rely on a Web Application Firewall (WAF) to block IDOR attacks. A WAF inspects request syntax for known attack patterns (such as SQLi or script injection), but it cannot decipher internal business logic. To a firewall, changing a course module ID from 1200 to 1201 looks like entirely legitimate application traffic.
Verification checklist: ensuring your VLE is patched
Deploying code and verifying full remediation are two distinct steps. It is common for production to be patched while staging or training instances—often populated with real student data—remain outdated and exposed.
1. Confirm the release in the administrative interface
Navigate to Site administration > Notifications. Check the footer string. You must see 4.5.16, 5.1.9, 5.2.5, or 5.3.1. Any lower revision indicates your instance remains vulnerable.
2. Verify code version via CLI
In your web root, inspect the $release declaration inside version.php:
grep -E '^\$release' version.php
If pulling from official Git repositories, running git describe --tags should match the patched release tag (e.g., v4.5.16). If you maintain bespoke code alterations, ensure the security commits have not been overwritten during merge conflicts.
3. Audit peripheral instances
Vulnerabilities in unmonitored staging environments represent an easy foothold. Inventory every server hosting production database dumps: test environments, QA sandboxes, container registries, and forgotten CPD portals. All must be updated or decommissioned.
4. Review third-party plugins
Under Site administration > Plugins > Plugins overview, filter for additional plugins. Audit Configurable Reports and review any custom plugins lacking active developer support.
5. Check access logs for exploitation attempts
If your system was unpatched following the disclosure date on 20/11, inspect your application logs. Under Reports > Logs, look for course module updates executed by teaching staff in courses where they lack valid enrolments, as well as unexpected deletions of Feedback templates. For MSA-26-0049, inspect query logs on your external enrolment database. Our infrastructure guide on Moodle server hardening post-PHP2Shell provides an end-to-end framework for host-level forensic analysis.
Remember also that PHP issued upstream security releases on 19/11. Running an up-to-date Moodle atop an unpatched PHP runtime leaves your stack exposed. We broke down those CVEs in our advisory on the PHP critical security updates.
Managed Moodle security with Agathas Web
With managed Moodle hosting from Agathas Web, addressing critical security bulletins does not require your internal IT team to manually triage vendor advisories. Our managed operations cover:
- Continuous vulnerability triaging. Whenever Moodle publishes an MSA, we immediately cross-reference your specific architecture (enrolment integrations, SCORM modules, multi-tenancy configurations) and provide clear risk assessments.
- Pre-deployment validation on staging across our Professional and Enterprise plans, using exact production mirrors before touching live services.
- Scheduled maintenance windows outside peak lecture and assessment hours, backed by full daily snapshots, 15-minute point-in-time binary logs, and routine monthly restore testing.
- Comprehensive perimeter and plugin audits, including automated alerting for third-party vulnerabilities like Configurable Reports.
- Enterprise-grade Moodle stack, equipped with Cloudflare enterprise WAF, proactive rate limiting on sensitive API routes, and 24/7 infrastructure monitoring backed by rapid-response engineering SLAs.
You retain full administrative control over pedagogy, course design, and governance, while we guarantee the resilience of the underlying platform. When an incident occurs, you deal directly with dedicated systems engineers on a 15-minute critical SLA.
To evaluate your exposure, book an infrastructure audit on our managed Moodle hosting page. Within three business days, we deliver a full inventory of your version health, plugin security, and surface risk. If your organisation is running Moodle 5.0 or older, we include an end-to-end migration roadmap.
Next steps: patch today and schedule 07/12
The Moodle 4.5.16 and 5.3.1 vulnerabilities rarely trigger perimeter firewall alerts; instead, they allow authenticated users to exceed their boundaries—whether that is a tutor accessing an unassigned regional cohort, cross-tenant course alteration in shared platforms, or compromised staff accounts reaching backend databases.
Your action plan is clear: audit all active environments, address external database enrolments and SCORM inputs first, and migrate off Moodle 5.0 immediately. Then, ensure 07/12/2026 is booked in your operational calendar for the release of 5.3.2 and 4.5.17.
If your organisation lacks the internal bandwidth to manage monthly security lifecycles, explore our managed Moodle hosting to eliminate this operational overhead.
Related posts

Moodle Workplace 5.3 Review: Multi-Tenancy, AI Limits and UK Business Impact
Multi-tenant unified accounts, 500-row AI limits, and an updated catalogue: what Workplace 5.3 delivers and how to replicate it on open-source Moodle.

Configurable Reports for Moodle: Critical Security Vulnerabilities and Remediation
Two critical CVEs have hit Moodle’s most popular reporting plugin. Discover whether your VLE is exposed and how to remediate without breaking faculty reports.

Coassemble Moodle Integration: Is the Certified Plugin Worth It for UK Teams?
Coassemble is now a Moodle Certified Integration. We compare it against H5P, SCORM, and the native editor, covering UK GDPR compliance, technical specs, and pricing.