Upgrade to Moodle 5.3 LTS from 4.5, 5.0, 5.1 or 5.2

Moodle 5.3 LTS was released on October 5, 2026, and Moodle 5.0 is now listed as no longer supported: it will not receive fixes for security risks. Cubite runs managed Moodle from $690 a month for up to 500 concurrent learners, with version upgrades and same-day CVE patching included. Cubite sells managed Moodle and publishes this guide; every Moodle fact below is from moodledev.io, checked on October 6, 2026.

Short answer (updated October 6, 2026): you can upgrade to Moodle 5.3 LTS directly from 4.4, 4.5, 5.0, 5.1 or 5.2. Before you do, make sure the server runs 64-bit PHP 8.3.0 or later with the sodium extension, that your database meets the new minimums (PostgreSQL 17, MySQL 8.4, MariaDB 11.4.0), and, if you are coming from 4.5 or 5.0, that your web server serves Moodle's new /public directory and your plugins have been moved into it.

Moodle 5.3 LTS at a glance

Which Moodle versions are still supported

If you run 5.0, upgrade first: it no longer gets security fixes. If you run 4.5 LTS, you have until October 4, 2027, which is time to test plugins on a staging copy rather than upgrade in a hurry. For the security releases that land between majors, see Moodle Security in 2026: The CVEs to Patch.

Upgrade it yourself, or have it managed

Cubite is one of the managed options and publishes this table. Managed Moodle at Cubite starts at $690 a month for up to 500 concurrent learners and includes version upgrades; see managed Moodle hosting and support.

The upgrade path from each version

From Moodle 4.5 LTS

Moodle 5.3 accepts upgrades from 4.4 or later, so a 4.5 site can go straight to 5.3. Three changes land at once: the /public web root (introduced in 5.1, see the next section), the PHP 8.3.0 minimum, and the higher database minimums. Check all three on a staging copy first.

From Moodle 5.0

Upgrade soon: 5.0 no longer receives security fixes. The path is the same as from 4.5: the /public web root, PHP 8.3.0 and the database minimums all apply.

From Moodle 5.1 or 5.2

Your web server already serves /public, so this is the lightest path. Check PHP (8.3.0 or later), the database minimums that 5.3 raised (PostgreSQL 17, MariaDB 11.4.0), and that each third-party plugin has a release that supports 5.3.

From Moodle 4.3 or older

Moodle 5.3 does not upgrade a site older than 4.4 directly. Upgrade to an intermediate release first (check that release's own notes for the versions it accepts), then to 5.3.

The /public web root (coming from 4.5 or 5.0)

Moodle 5.1 introduced a new /public directory. Moodle's 5.1 release notes say: "Your web server now needs to be configured so that its document root points to this /public directory, rather than the main Moodle folder." Sites that skip this step can show directory listings or error messages after the upgrade.

• Point the web server's document root at the /public directory inside your Moodle code, not at the Moodle folder itself.
• Move your plugins. The 5.1 notes say plugins installed before the upgrade "will still be in their original locations above the /public folder" and "will need to be manually moved into the appropriate location within the /public directory".
• Keep config.php and the command-line scripts where they are: in the 5.3 code, config-dist.php and admin/cli/upgrade.php sit at the top of the Moodle folder, outside /public.
• Moodle 5.1 also added a routing engine. Moodle recommends it but says it is not compulsory, and a compatibility layer keeps older URLs working.

Pre-upgrade checklist

Step by step

1. Turn on maintenance mode (admin/cli/maintenance.php --enable) and stop cron.
2. Take the backups from the checklist.
3. Replace the Moodle code with 5.3, for example by checking out the MOODLE_503_STABLE branch, and keep your existing config.php.
4. If you are coming from 4.5 or 5.0, point the document root at /public and move the plugins into it.
5. Run the upgrade from the command line: php admin/cli/upgrade.php.
6. Turn maintenance mode off, start cron again, and test logins, enrollments, grading and your plugins.

Rollback

A major upgrade changes the database, so the way back is the backup you took in step 2: restore the database and moodledata, put back the previous code and web server configuration, then turn maintenance mode off. Test that restore before the upgrade, not during it.

Moodle 5.3 and AI providers

Moodle 5.3 adds an Anthropic Claude AI provider plugin (MDL-88674) and AI user reporting (MDL-80893). Moodle's AI subsystem, part of core since 4.5, stays off until a site administrator enables a provider and enters that provider's API key.