What Happened
On October 21, 2026, the PHP project released fixes for two critical security flaws (CVE-2026-109618 and CVE-2026-109619, nicknamed PHP2Shell). PHP is the programming language behind most WordPress sites and many other websites. Left unpatched, the flaws could let an attacker run code on a web server without logging in.
Details leaked the day before the fixes shipped. On October 26 the US cybersecurity agency CISA added both flaws to its list of vulnerabilities known to be exploited. Security firms say most attack attempts failed, but one researcher recorded a successful attack against a decoy server set up to attract them.
The fixed versions are PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP 8.1 and older no longer get regular updates, so those sites depend on their host to apply a fix. PHP 8.2 stops getting security updates on December 31, 2026.
WordPress says this is not a WordPress flaw and that no WordPress update is needed. Updating WordPress or your plugins does nothing here. The fix happens on the server.
What It Means for Your Business
Your host usually controls your PHP version, and many hosts have already patched. Do not assume yours did. Check.
In your WordPress dashboard, go to Tools, then Site Health, then Info, then Server. If the PHP version shown is at or above the fixed numbers above, you are covered. If it is lower, that does not always mean you are exposed, because some hosts patch older versions in their own packages. It does mean you should ask them.
If nobody manages your site, that is the real problem. Unmanaged sites are the ones that sit on old PHP for years.
Patchstack warns against “fix” plugins and copied code snippets. Updating PHP is the only complete fix. Temporary settings reduce risk but do not make a site safe.
Want someone to check your site’s PHP version and talk to your host? Steven Digital can do that.
FAQ
No. WordPress says no core update is needed. The PHP version on your server is what matters.
Nothing in this alert says so. Patchstack lists signs to watch for, such as sudden memory-limit errors or server errors. If you see those, patch first and have someone check the site.