SIGNAL FEED
Checking the latest publisher announcements…
All signals
EDITORIAL · OCT 22, 2026

A PHP bug just killed two decade-old Japanese games: World Quest and Please Save My Pandemonium! shut down overnight

World Quest and JAGS' Please Save My Pandemonium! ended service with no countdown after critical PHP vulnerabilities surfaced around Oct. 21, 2026. Their old servers couldn't be safely patched.

Most games get a shutdown countdown. Two months, a farewell event, a last sale on premium currency. World Quest and Please Save My Pandemonium! got about one day, and the reason was a programming language.

Around October 21, 2026, critical vulnerabilities were disclosed in the core of PHP, the server-side language that a large share of web and mobile game backends run on. Inven Global reports them as CVE-2026-109618 and CVE-2026-109619, nicknamed "PHP2Shell," scored 9.2 on CVSS v4.0, and allowing remote code execution without authentication. In plain terms: send the right request, maybe own the server.

Patches landed quickly for supported versions (8.5.12, 8.4.27, 8.3.36, 8.2.35 and up). That helps if your game runs on a supported version. Two of them did not.

World Quest: shut down the same day

On October 21, the official World Quest account posted on X that a serious vulnerability had been found in the PHP its servers use, that the old system couldn't be adequately protected, and that service was ending that day to protect players' information.

World Quest is a virtual travel game with roughly 15 years behind it. It has died before: it ended service in 2019, then came back in 2020 so people stuck at home during the pandemic could travel somewhere, even if only in a browser. Its second run lasted about six years. Its second ending came with no notice at all.

Please Save My Pandemonium!: "not realistic" to migrate

On October 22 Japan time, developer JAGS posted an end-of-service notice for Please Save My Pandemonium! (僕の魔界を救って!), an idle fantasy strategy RPG where you send monster armies out on real-time sorties to retake a captured underworld.

The notice is unusually candid. The game has been running for more than 10 years on what JAGS calls a fairly old environment, PHP included. The team kept patching where it could and kept the servers up even as the player count dropped, because it wanted the place to stay open. This time, JAGS says, the problem can't be handled safely on the current system and hardware, and moving the OS and PHP to a modern stack isn't realistic. It won't keep running with players' data exposed, so the game is done.

JAGS also says it doesn't want this to be the end of the game itself, and that it would like to come back to the underworld "in a different form" someday. It makes no promises, and says so.

Who else got hit

Bigger Japanese live-service games went into emergency maintenance instead of ending. Inven Global lists Princess Connect! Re:Dive, Uma Musume: Pretty Derby, Shadowverse: Worlds Beyond, Another Eden and Heaven Burns Red among them. Those run on newer infrastructure, patched, and began coming back early on October 22.

Can I still play either game?

No. Both shut down effective immediately. Neither announcement mentions an offline version or data export.

Why this one matters

Shutdowns usually come down to money: revenue drops below the cost of keeping servers on. This is the other risk for small, old online games: technical debt. A decade-old backend that nobody can safely upgrade keeps working right up until one disclosure makes it a liability. Then a small team chooses between its players' data and its game, and the honest answer is the game.

Expect a few more of these if other legacy servers turn out to be stuck on unsupported PHP versions. We'll add them as they're confirmed.

Sources

Published Oct 22, 2026. Based on JAGS' official Please Save My Pandemonium! end-of-service notice (Oct. 22, 2026) and the World Quest X post quoted by Automaton, with Inven Global reporting. No game artwork used.

STEAM APP EXPLORER

Check any Steam game.

Enter a Steam App ID to fetch its current player count directly from Steam.

Find the ID in a Steam store URL: store.steampowered.com/app/730/. Counts cover Steam only.