When php2shell took Moodle offline: what the big hosts did
On 21 October 2026 Open LMS took every hosted Moodle site offline, mid-exam, and Moodle HQ pulled its own sites. What happened hour by hour and what to plan for next time.
On 21 October 2026, a student at Loyola University Maryland was on question 40 of a 50-question marketing exam when everyone in the room started looking around. Moodle was gone. Their host, Open LMS, had taken every customer site offline because of two PHP bugs that the world would soon call php2shell.1
Moodle HQ did the same with its own public sites. So did governments, banks and hospitals across Europe. For one day, switching your site off was the responsible thing to do.
We explained the bugs themselves in php2shell explained. This post is about the response: who did what, how fast, and what a Moodle site should have ready before the next one.
What happened, hour by hour?
All times UTC, from UptimeRobot’s reconstruction and the vendors’ own updates:2
| When | What |
|---|---|
| 17 Oct | Amazon’s threat intelligence team records the first exploitation attempt |
| 20 Oct, about 15:00 | The CVE numbers leak, with a wrong release time |
| 20 Oct, 19:30 | PHP publishes an advance notice and moves the release up a day |
| 21 Oct, 03:02 | Cloudflare’s WAF rules go live |
| 21 Oct, 07:41 | Chainguard ships fixed container images, six hours early |
| 21 Oct, 13:41 | Open LMS warns it will take all customer sites offline within minutes1 |
| 21 Oct, 14:00 | PHP releases 8.5.12, 8.4.27, 8.3.36 and 8.2.35 |
| 21 Oct, 14:11 | A widely used Ubuntu PHP package repository starts returning errors |
| 21 Oct, 15:41 | Open LMS confirms all customer sites are offline1 |
| 22 Oct, 23:47 | Open LMS reports its last region patched and every site back online3 |
(The Loyola report gives Open LMS’s times in US Eastern time, 9:41 and 11:41 in the morning. We converted them.)
So the fastest large Moodle host needed about a day and a half to bring every site back. That is not slow. Patching thousands of sites, testing that Moodle still works on each one and bringing them back region by region takes time. It just means a hosted Moodle site was down for most of a working day, with no warning, during exam season.
What did Moodle HQ do?
Moodle HQ took its sites offline as a precaution after the disclosure, patched them, and brought them back the next day, then kept rolling patches out to the client sites it hosts.4 Its status page later said patches were on every hosted client site, all of them were online, and its security team found no evidence the bugs were exploited on Moodle-hosted sites or that client data was accessed.5
For self-hosted sites, HQ’s advice was short: update PHP now, because unpatched sites stay vulnerable.5 That is the part nobody can do for you.
Was taking sites offline the right call?
For a host with thousands of sites and no way to patch them all in an hour, yes. The bugs allowed remote code execution, exploitation had started days before the fix, and Cloudflare reported millions of attempts that week.6 A site that is off can’t be taken over. Governments did the same: the Dutch National Cyber Security Centre, DigiD and the Czech government website all went dark.2
But “everything off” is what you do when you have no smaller tool. A site that sits behind a web application firewall had rules from 03:02 UTC, eleven hours before the PHP release. A site that builds its PHP from container images could have had fixed images from 07:41. Those sites could stay up.
What should a Moodle site have ready for next time?
php2shell will not be the last bug like this. The PHP Foundation runs on one full-time employee and 14 mostly part-time contractors, by its director’s own account, while proposed changes to PHP nearly doubled in a year.6 More bugs will be found faster, by people and by AI tools. Plan for the next one now.
- Know who patches your PHP. On managed hosting, your host. On your own server, you. On “managed” hosting that only manages the server, find out today which one it is.
- Run a PHP version that still gets fixes. The php2shell fixes went to 8.2 and newer only. PHP 8.2 itself stops getting fixes on 31 December 2026. More in outdated PHP under Moodle.
- Don’t depend on one package source. The Ubuntu repository many servers use buckled within minutes of the release. Know your second option: distribution packages, official Docker images or building from source.
- Put a WAF in front of Moodle. It buys you hours, and on 21 October hours were the difference between staying up and switching off.
- Have a maintenance mode plan. Moodle’s own maintenance mode (
admin/cli/maintenance.php --enable) shows a page you control, instead of a host’s error page. Decide in advance who can turn it on. - Protect exams. A timed quiz keeps counting while the site is down. Know how your “when time expires” setting will treat those attempts, make sure teachers know how to grant a user or group override, and agree in advance what happens to an exam cut off by an outage. Loyola’s students found out live.
- Keep a status page and a way to reach users that doesn’t run on Moodle. If Moodle is your only channel, an outage is also a communications blackout.
- Test your custom plugins on new PHP releases early. The fastest way to block an emergency PHP upgrade is a plugin that breaks on it. This is the part of a care plan that pays for itself.
The short version
The hosts did the responsible thing, fast, and their customers still lost most of a day. The sites that stayed up had done their work earlier: current PHP, a firewall, a second package source and a tested upgrade path for their own code. None of that is expensive. All of it has to happen before the bug is announced.
Sources
-
The Greyhound (Loyola University Maryland), Moodle temporarily disabled after security threat concerns, 21 October 2026. ↑ ↑ ↑
-
UptimeRobot, Inside php2shell: why websites took themselves offline. ↑ ↑
-
Open LMS, status page incident history, update of 22 October 2026, 23:47 UTC. ↑
-
Moodle on X, post of 22 October 2026; Moodle.org forum, Update on Moodle’s response to the PHP2SHELL vulnerability. ↑
-
Moodle, status page. ↑ ↑
-
Slashdot, PHP Foundation “under-funded” with one full-time staff member, director says, summarising Reuters, 24 October 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