If you run a WordPress website, you probably update WordPress and your plugins when prompted. That habit is good, but this time it is not enough. The flaw is not in WordPress. It is in PHP, the language WordPress runs on.
What happened
On 21 October 2026, the PHP project released emergency fixes for two critical flaws, CVE-2026-109618 and CVE-2026-109619, now widely called PHP2Shell. Both are rated 9.2 out of 10, and both can let an attacker run code on a server without logging in. The flaws were found with help from AI tools, and details leaked online before the fixes were ready, so attacks began quickly. The United States cybersecurity agency CISA added both flaws to its list of known exploited vulnerabilities on 26 October, and security researchers have reported attack traffic since. A third related issue, CVE-2026-115560, was announced on 23 October and is not fixed in these releases yet. This is a different flaw from the WordPress Core flaw listed by CISA earlier this week. That one was in WordPress itself, and a WordPress update fixed it. This one sits underneath WordPress, so the fix has to come from the server.
What it means for a small business
Almost every WordPress site runs on PHP, so this is not a flaw in one plugin or one theme. It is in the engine underneath your whole site. If an attacker gets in through it, they can change your pages, take customer details from your database, or use your site to attack others. And because the flaw is in PHP itself, no WordPress update, plugin update or theme update will close it. Only a PHP update does that. Many hosts apply PHP updates for you, so your site may already be safe. But if your host has not updated, or your site runs on an old PHP version, it is still exposed.
What to do about it
First, find your PHP version. In WordPress, go to Tools, then Site Health, then the Info tab, and look under Server. Or ask your host. Second, check it against the fixed versions: PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35. Anything at or above those, in the same branch, is fixed. Third, if your version is lower, contact your host and ask in writing whether the PHP2Shell fix is applied and when. If you run your own server, update PHP and restart the web server and PHP workers. Fourth, if your site runs PHP 8.1 or older, plan an upgrade. The PHP project no longer releases fixes for those versions, and PHP 8.2 reaches the end of its support on 31 December 2026, so 8.3 or newer is the sensible target. Fifth, do not install a plugin that claims to fix PHP2Shell, and do not paste code from a forum or social post. The only complete fix is the PHP update. A setting change that turns off session upload progress blocks only one attack path and is not a full fix. Finally, check your site for changes you did not make, and make sure your backups are current.
A website is only as safe as the software underneath it. This is the kind of check that belongs in regular website care, and it takes one message to your host. Digilistan builds and maintains WordPress websites for small businesses, and this is exactly the sort of check we run as part of that work.
