Since 21 October 2026, “update PHP now” has been everywhere, usually next to “WordPress sites at risk”. If you run a WordPress site, the reasonable questions are: is mine affected, is there a WordPress update for this, and is it my job or my host’s?
The short answer: WordPress itself doesn’t need an update, and no plugin can fix this. What matters is the PHP version your server runs. On managed or shared hosting, patching PHP is your host’s job, and yours is to check that they did. If your site runs PHP 8.1 or older, you need to switch to a newer version.
What happened, briefly
Two critical bugs were found in PHP, the language WordPress runs on. They’re nicknamed PHP2Shell (CVE-2026-109618 and CVE-2026-109619), and they let an attacker run code on a server without logging in. Researchers showed it working against standard WordPress setups, and attacks started before the fix was out. The full technical story is in our guide to the vulnerability itself.
The fix arrived on 21 October in these PHP versions:
| If your site runs | It’s fixed from |
|---|---|
| PHP 8.5 | 8.5.12 |
| PHP 8.4 | 8.4.27 |
| PHP 8.3 | 8.3.36 |
| PHP 8.2 | 8.2.35 |
| PHP 8.1 or older | No official fix: switch to a newer PHP version |
Why updating WordPress won’t fix it
The bugs are inside PHP, below WordPress. Think of PHP as the engine and WordPress as the car: a new dashboard doesn’t fix a faulty engine. That’s why:
- Updating WordPress, your theme or your plugins doesn’t protect you. Keep them updated anyway, for their own security fixes, but they’re unrelated to this.
- Security plugins can’t patch it. They run on top of PHP, after the vulnerable code has already run.
- Skip any “PHP2Shell fix” plugin or code snippet. Nothing at the WordPress level can patch PHP, and unverified snippets can break your site or worse.
Who needs to act?
It depends on who manages your server.
- Managed WordPress hosting (the host runs the server and WordPress for you): the host patches PHP. Many large hosts confirmed protection within a day or two. Your part is to confirm yours did.
- Shared hosting (cPanel, Plesk and similar): the host patches PHP for everyone on the server. Your part is to confirm it, and to check which PHP version your site uses, because many control panels let each site pick an older one.
- A VPS or your own server, including setups managed through tools like Laravel Forge, Ploi or RunCloud: nobody patches it for you. Whoever runs the server has to install the update and restart PHP. Follow the steps in the technical guide.
- You manage sites for clients: go through every site, staging copies included. Old sites on old PHP versions are exactly what attackers scan for.
Step 1: Check your PHP version
In your WordPress dashboard, go to Tools → Site Health, open the Info tab and expand Server. The PHP version is listed there. Most hosting control panels also show it, usually under a “PHP version” or “PHP selector” setting.
Compare it with the table above. There’s one catch: many hosts apply the fix without changing the version number, so a site can be patched and still show, say, 8.3.35. The number tells you whether you’re on a supported branch; only your host can confirm the patch itself.
Step 2: Ask your host
A short message gets a clear answer. Copy this into a support ticket:
Hello,
Regarding the PHP security release of 21 October 2026(CVE-2026-109618 and CVE-2026-109619):
1. Have you applied the fix on the server that runs my site?2. Which PHP version is my site using right now?3. If my PHP version is no longer supported, what's the easiest way to switch to a newer one?
Thank you.Many hosts have also published a status page for this; check it first, since your answer may already be there.
Step 3: If you’re on PHP 8.1 or older
These versions get no fix from the PHP project, so the safe path is a newer PHP version. PHP 8.2 stops receiving security fixes at the end of 2026, so PHP 8.3 or 8.4 is the better choice if your site supports it.
Switching is usually a dropdown in your control panel, but do it carefully:
- Take a full backup, files and database, or make sure your host has a recent one.
- Use a staging copy if your host offers one, and switch PHP there first.
- Switch PHP, then check the pages that matter: the homepage, checkout, contact forms, logins, and anything that earns you money.
- If something breaks, it’s almost always one plugin or theme that isn’t ready for the newer PHP version, not the whole site.
That last step is where people get stuck. Rather than switching every plugin off on a live site, find the one plugin that breaks, update or replace it, and stay on the new PHP version. Culprit Finder does exactly this for your browser only, while visitors keep the working site. If PHP’s new version gives you a white screen or a critical error, these guides help: white screen of death and “There has been a critical error”.
An extra layer, not a fix
If your site uses Cloudflare, it has turned on firewall rules for these attacks on every plan, including Free. That’s worth having while your host finishes patching, but it only filters traffic that goes through Cloudflare. It doesn’t replace the PHP update.
Was my site hacked?
Attacks started on 17 October, before the fix was public, so a site that ran unpatched PHP since then could have been probed. Things worth checking:
- unknown administrator accounts under Users
- files you didn’t upload, especially
.phpfiles inwp-content/uploads - unexpected redirects, pop-ups or spam pages in search results
- a warning from your host or a security scanner
If anything looks wrong, ask your host to check the server logs from 17 October onwards, restore a clean backup from before that date if you can, and change your passwords. Finding none of these isn’t a guarantee, so if your PHP was unpatched for days, asking your host to look is worth the five minutes.
Questions people are asking
Is there a WordPress update for this? No. The fix is in PHP, so updating WordPress changes nothing here.
Do I need to update my plugins? Not for this, though keeping plugins updated is still good practice. It does matter if you switch PHP versions: an outdated plugin is the most common thing to break when PHP changes.
My host says I’m protected but my PHP version looks old. Who’s right? Probably your host. Patched packages often keep the old version number. If you’re on PHP 8.1 or older, plan the switch anyway: those versions no longer get fixes from the PHP project.
Does Culprit Finder protect me against this? No, and no plugin can. Culprit Finder is a troubleshooting tool. Where it helps is the step after: if switching to a newer PHP version breaks something, it tells you which plugin is responsible.