Moodle LMS 5.3.1 explained: upgrade error, H5P, token fixes
What Moodle 5.3.1, 5.2.5, 5.1.9 and 4.5.16 fix: 17 security advisories, the 5.3 upgrade error, the H5P regression, a grading bug, token alerts, and the end of 5.0.
Short answer: if you run Moodle 5.3, 5.2, 5.1 or 4.5, update to the 12 November 2026 point release (5.3.1, 5.2.5, 5.1.9 or 4.5.16). Every one of them carries security fixes.1 If you run 5.0, there is a 5.0.12, but it has no security fixes, because security support for 5.0 ended on 5 October 2026.2 Plan the move to 5.3, the current long-term support release.
5.3.1 is the first point release of the new long-term support version, and it is the one most 5.3 upgrades should have waited for. Here is what it fixes, and what it tells you about the 5.3 upgrade path. The next point releases (5.3.2, 5.2.6 and 4.5.17) are planned for 7 December 2026.3
Which versions came out, and what do they fix?
| Version | Security fixes | Other notable fixes |
|---|---|---|
| 5.3.1 | Yes | Upgrade error, H5P offline, quick grading permissions, token and OAuth 2 changes, about 40 fixes in total |
| 5.2.5 | Yes | H5P offline, quick grading permissions, password reset tokens |
| 5.1.9 | Yes | H5P offline, an assignment grading error |
| 4.5.16 | Yes | H5P offline |
| 5.0.12 | No (support ended 5 Oct 2026) | H5P offline only |
As is usual for Moodle, the release notes said only that “a number of security related issues were resolved”, with details to follow “after a period of approximately one week”, so admins could update first.1 The details came out on 20 November 2026.
The 17 security advisories
Moodle HQ published 17 advisories on moodle.org/security, MSA-26-0046 to MSA-26-0062.4 HQ rates 13 of them serious and 4 minor. All but one are fixed in 5.3.1, 5.2.5, 5.1.9 and 4.5.16. MSA-26-0062 lists fixes in 5.1.9 and 4.5.16 only.
Most of them are the same kind of bug: an IDOR (insecure direct object reference). The code takes an id from the request and acts on that record without checking that the user may reach it. In a Moodle site, that means a teacher in one course reaching into another. The advisory for the wiki, for example, says users could view wiki page versions from courses they could not otherwise access and copy that content into their own wiki.5
| Advisory | What it was | Risk |
|---|---|---|
| MSA-26-0049 | SQL injection risk in the external database enrolment plugin | Serious |
| MSA-26-0047 | Arbitrary file read risk in Blackboard question import | Serious |
| MSA-26-0051 | Stored XSS risk in the SCORM objectives report | Serious |
| MSA-26-0050 | Activity editing could modify activities in other courses | Serious |
| MSA-26-0052 | Missing access checks in the quiz question bank fragment callback | Serious |
| MSA-26-0053, 0054, 0056 to 0059, 0061, 0062 | IDORs in Feedback templates, badge alignments, forum lock and subscription web services, wiki versions, Lesson page editing, quiz sections, quiz overrides and the quiz random question filter | Serious |
| MSA-26-0046, 0048, 0055, 0060 | Missing checks in grade feedback, grade items and single view grade web services, and glossary entries from other courses | Minor |
Three of them stand out:
- External database enrolment (MSA-26-0049). If your site syncs enrolments from a student information system through
enrol_database, this one is yours. It is a core plugin, so updating Moodle fixes it. - Blackboard question import (MSA-26-0047). Importing questions means uploading a file, so on most sites any teacher can reach this code. Update soon if teachers can import questions.
- Web services. Five advisories name a web service. They matter most on sites where the Moodle app is enabled or where integrations call the API with user tokens, because that is where those functions are reachable.
For plugin developers, the pattern is the lesson. An IDOR like these usually means the code checked capabilities in the context the user came from, not in the context of the record the id points to. In Moodle that is validate_context() and require_capability() against the record’s own context. Check your own web services and AJAX callbacks for the same thing.
The rest of this post covers what the release notes said on release day.
The 5.3 upgrade error: a 500 on every page
If you upgraded to 5.3.0 and every page returned HTTP 500 with an error about core\composer and $vendordir, you were not alone. MDL-90273 describes it exactly:6
- You replace the code with 5.3 and copy
config.phpback. - Before you run the upgrade, any normal page fails with
Entry "core\composer" cannot be resolved: Parameter $vendordir of __construct() has no value defined or guessable. - Opening
/adminpurges the caches, and after that pages load again.
The cause had nothing to do with Composer. In 5.3, core\composer gets its vendor directory from a hook callback registered in lib/db/hooks.php. The cached list of hook callbacks and the compiled dependency injection container in moodledata were still from the old version, so the callback was missing. The issue says sites coming from 4.5.15, 5.1.8 and 5.2.4 are all likely affected.6
Because the message mentions Composer, admins went looking for a Composer problem. The tracker issue links a forum thread where one admin rolled back to 5.2.2 and ran composer install before trying again.6 None of that was needed.
What to do: if you upgrade by replacing code, run php admin/cli/purge_caches.php or php admin/cli/upgrade.php before anyone opens the site, which is good practice anyway. 5.3.1 fixes the error itself.
A second 5.3 fix in the same area: the new REST API endpoints accidentally required Composer dependencies to be installed (MDL-90494).7 HQ intends Composer to be mandatory later, from 6.0, but not in 5.3, so 5.3.1 adds lightweight fallbacks. If you saw REST API errors on a site installed from the zip package, this is why.
H5P stopped working offline, because of a security fix
On 5 October, Moodle fixed MSA-26-0044, “Missing access checks on H5P content files”, in 5.2.4, 5.1.8 and 4.5.15.8 A side effect: H5P packages stopped working offline in the Moodle app. MDL-90215, opened on 22 October, says the regression was caused by MDL-89547, an issue the public cannot view.9 Combine the two release notes and MDL-89547 is very likely the tracker issue behind MSA-26-0044, but that is our inference, not something HQ has stated.
The fix is in all five releases, including 5.0.12, under Moodle’s regression backporting policy.2 If your learners use H5P in the app, for example on field placements or in places with poor signal, this update matters more to them than any other line in the notes.
The lesson is ordinary but worth saying: access checks on files are hard to add without breaking a client that fetched those files another way. Test the mobile app after any security update that touches content files.
Graders could release grades without permission
MDL-90205, fixed in 5.3.1 and 5.2.5: in assignment quick grading, the code that saved grades did not check the marking workflow state a user submitted against their capabilities. A grader without mod/assign:releasegrades or mod/assign:managegrades could release grades by submitting the state released.10
This was filed as a normal bug, not a security advisory. It still matters if you use marking workflow so that grades stay hidden until a moderator releases them. On 5.1 and 4.5, the release notes do not list this fix, so check whether your markers have quick grading enabled and who holds which capability.
Tokens: alerts, logs and old reset links
5.3 introduced personal access tokens and an OAuth 2 server for the new REST API. 5.3.1 adds the monitoring that should have come with them:1
- A user is notified when a personal access token is created on their account, and admins are notified when an OAuth 2 client secret is created (MDL-89760). The issue says why: an unexpected token “is what catches a compromised account”.11
- Users are warned before a personal access token expires (MDL-89442), and notified when an OAuth 2 client secret has expired and was not rotated (MDL-90024).
- Creating, editing and deleting OAuth 2 clients is now written to the admin config log (MDL-89990).
- Invalid, expired or revoked tokens return a proper error instead of a 500 (MDL-89848).
One fix reaches 5.2.5 as well: password reset links are now invalidated when the account’s email address changes or a new reset is requested (MDL-69961).12 Before, a reset link sent to an old address stayed valid until it expired. The issue was opened in October 2020 and resolved in October 2026. The issue rates the risk low, since the tokens are short-lived and single use, but it is a real gap if an attacker controls an old mailbox.
Two fixes plugin developers should notice
- TinyMCE plugins could change other TinyMCE plugins’ settings (MDL-89492, 5.3.1 and 5.2.5). Every plugin’s
configurecallback received the same options object by reference, so one plugin could, for example, remove the “Browse repositories” button from the link dialog.13 If your editor plugin changed shared options on purpose, test it on 5.3.1. - Building the theme CSS got much slower with dark mode (MDL-90109). The issue reports the Boost theme CSS build going from about 5 seconds to about 25 in the reporter’s environment, which slows upgrades, cache purges and Behat runs.14 5.3.1 includes a performance fix for it. If you build a custom theme on Boost, measure your own build time after updating.
Also that week: a critical hole in Configurable Reports
Two days before the point releases, on 10 November 2026, Moodle HQ posted a warning on moodle.org/security about a critical vulnerability in Configurable Reports (block_configurable_reports), a popular third-party plugin, not part of Moodle itself.15 HQ did not describe the flaw. The maintainer had submitted a fixed version to the plugins directory, and HQ’s advice was to update as soon as it is available, or to disable or uninstall the plugin until then.
Updating Moodle core does not touch it. If the plugin is installed, check its version under Site administration > Plugins > Plugins overview, and update it on its own.
What we would do this week
- Update to 5.3.1, 5.2.5, 5.1.9 or 4.5.16, on a test copy first if you have custom plugins.
- Purge caches from the command line as part of every code replacement, before the site takes traffic.
- Test H5P in the Moodle app if your learners use it offline.
- Check the advisories against your site: external database enrolment, question import and the Moodle app first. If you write plugins, look for the same missing checks in your web services.
- If you use Configurable Reports, update it or switch it off until you can.
- If you are on 5.0, start the upgrade now. Our Moodle 5.3 and 4.5 requirements guide lists what the server needs, and What breaks when you upgrade Moodle covers the plugins.
If a custom plugin is what keeps you on an old version, we can update it for 5.3 at a fixed price.
Sources
-
Moodle developer docs, Moodle 5.3.1 release notes, 5.2.5, 5.1.9 and 4.5.16, all dated 12 November 2026. Read 18 November 2026. ↑ ↑ ↑
-
Moodle developer docs, Moodle 5.0.12 release notes: “security support for 5.0.x ended on 5 October 2026.” ↑ ↑
-
Moodle developer docs, Releases, target dates, read 19 November 2026. ↑
-
Moodle.org, Security announcements, MSA-26-0046 to MSA-26-0062, all posted 20 November 2026. Read 21 November 2026. ↑
-
Moodle.org, MSA-26-0057: IDOR allows viewing of wiki page versions from other courses, CVE-2026-133070, tracker issue MDL-89477, 20 November 2026. ↑
-
Moodle Tracker, MDL-90273: Upgrading to 5.3: core\composer error on every page until caches are purged. ↑ ↑ ↑
-
Moodle Tracker, MDL-90494: OpenAPI Routes require Composer dependencies and should not in 5.3. ↑
-
Moodle developer docs, Moodle 5.2.4 release notes, 5 October 2026, and the notes for 5.1.8 and 4.5.15. ↑
-
Moodle Tracker, MDL-90215: H5P packages do not work offline anymore, regression created by MDL-89547. ↑
-
Moodle Tracker, MDL-90205: Assignment quick grading can release grades without the required permissions. ↑
-
Moodle Tracker, MDL-89760: Notify users and admins when a personal access token or client secret is created. ↑
-
Moodle Tracker, MDL-69961: Forgot password tokens should be invalidated when account email address changes or a new token is requested. ↑
-
Moodle Tracker, MDL-89492: TinyMCE plugins can modify other TinyMCE plugins’ configurations. ↑
-
Moodle Tracker, MDL-90109: Building the theme CSS is much slower since the dark colour mode was added. ↑
-
Moodle.org, Configurable Reports plugin - critical vulnerability fix, Moodle HQ, 10 November 2026. Read 19 November 2026. ↑
Need a Moodle plugin built or rescued?
Tell the scoping assistant what you need. You get a fixed price and a timeline in a few minutes, and an engineer reviews it within one business day.
Get a fixed quote