Someone’s been jiggling the locks on WordPress websites (here’s what to do) 🗝️

If your inbox has suddenly filled up with scary-sounding emails from your hosting company, you’re not alone. On 21 October 2026, the team behind PHP released an urgent fix for a security flaw now nicknamed PHP2Shell, and every WordPress website owner needs to know about it.

Picture this: you find out the locks on almost every house on your street share the same fault. It isn’t your paint colour or your new kitchen that’s the issue. It’s the lock on the front door, and anyone who knows the trick could let themselves in without a key.

That’s PHP2Shell in a nutshell. The good news? The new locks are already here, and fitting them is usually quick. Here’s what’s going on, how to check your own website in about a minute, and what to do next.

What is PHP2Shell?

PHP2Shell is the nickname for two critical security vulnerabilities in PHP, officially tracked as CVE-2026-109618 and CVE-2026-109619. Both are rated 9.2 out of 10 for severity, which puts them firmly in the “critical” category.

PHP is the engine that quietly runs every WordPress website behind the scenes. Most people never think about it, the same way you don’t think about the wiring in your walls until something goes wrong.

What makes PHP2Shell serious is that, on a server that hasn’t been patched, an attacker could potentially run their own code on your website without needing to log in. No password, no back door, just a cleverly crafted visit to your site.

The PHP team released fixed versions on 21 October 2026. There were also unconfirmed reports of early attacks around the same time, so this one is worth acting on now rather than “when you get a chance”.

If you’d like the deeper story, Wikipedia has a good overview of PHP2Shell, and the official PHP security announcement has the technical details.

Is my WordPress website affected by PHP2Shell?

If your website runs on WordPress, the short answer is yes, until your PHP has been updated. Every WordPress site runs on PHP, so every WordPress site is in scope.

Here’s the bit that catches people out: WordPress automatic updates won’t fix this. The flaw isn’t in WordPress, your theme or your plugins. It’s in PHP itself, which lives on your hosting server, a level below your website.

Think of it this way: WordPress updates repaint the walls and fix the leaky taps. PHP is the foundation and the front door lock. Your hosting company looks after that part, and they need to fit the new lock.

Websites at the highest risk are the ones running older versions of PHP. Versions 8.1 and earlier won’t receive an official fix at all, so those sites need moving to a newer version as soon as possible.

How to check your WordPress PHP version (in about a minute)

You don’t need to be technical for this one. If you can log in to WordPress, you can check.

  1. Log in to your WordPress dashboard.
  2. Go to Tools > Site Health, then click the Info tab.
  3. Click Server to expand it, and look for PHP version.

Then compare your number with the table below.

Your PHP version Patched version to look for What it means
8.5 8.5.12 or higher Patched once your host updates
8.4 8.4.27 or higher Patched once your host updates
8.3 8.3.36 or higher Patched once your host updates
8.2 8.2.35 or higher Patched, but 8.2 stops getting security fixes on 31 December 2026
8.1 or lower No fix available Needs upgrading to a newer version

A quick heads-up: some hosting companies (especially those using CloudLinux, like VentraIP) apply the fix without changing the version number. So your site might still show 8.3.35 or 8.4.26 and actually be patched. If your number looks old, check your host’s status page or ask them directly whether the PHP2Shell fix has been applied.

If your number is lower than the one in the middle column, or it all looks like gibberish (totally fair!), keep reading.

What to do next to protect your website

The fix depends on which PHP version you found.

If you’re on PHP 8.2, 8.3, 8.4 or 8.5: your hosting company needs to apply the patched release. Most good hosts are already on it. Check their status page or send a quick support message asking when the update will be live on your server. Some hosts let you choose the patched version yourself in cPanel’s PHP selector.

If you’re on PHP 8.2: once you’re patched, plan a move to PHP 8.3 or higher before the end of the year. 8.2 retires on 31 December 2026 and won’t get any more security fixes after that.

If you’re on PHP 8.1 or older: there’s no official fix coming for your version, so your website needs to move to a newer one. This is the step that needs a careful hand. Changing PHP versions can break older themes and plugins, so take a full backup first, switch the version, then check your forms, pages and any bookings or shop features.

A quick word of warning: some articles suggest switching off certain PHP settings as a workaround. Those measures only reduce some of the risk. The PHP team is clear that updating is the only complete fix.

Rather not deal with it? Let us fix it for you

If all of this sounds like a job you’d happily hand to someone else, we’d love to help. At Ola Digital, we look after WordPress websites for professional service businesses across Brisbane and Australia, and we’re working through PHP2Shell fixes right now.

For $179 + GST, we’ll:

  • Check which PHP version your WordPress website is running
  • Confirm with your hosting company that the security fix has been applied (and nudge them if it hasn’t)
  • Run a security scan and check your WordPress, theme and plugin updates
  • Send you a short, plain-English summary of what we found

If your website needs moving to a newer PHP version, we’ll take a full backup, test everything and send you a quote before doing any extra work. No surprises.

Book your PHP2Shell fix here →

We’re working through requests in the order they come in, so the sooner you book, the sooner your locks get changed.

Want this handled for you every time?

This is exactly the kind of thing our WordPress maintenance plans take care of. Our maintenance clients didn’t have to lift a finger this week; we checked, chased and patched their websites for them. If you’d like that peace of mind for the next one, book a quick chat and we’ll walk you through it.

PHP2Shell FAQs

What is PHP2Shell?

PHP2Shell is the nickname for two critical PHP security vulnerabilities, CVE-2026-109618 and CVE-2026-109619. On an unpatched server, they can let an attacker run code on a website without logging in.

Does PHP2Shell affect WordPress?

Yes. Every WordPress website runs on PHP, so every WordPress website is affected until its PHP version is patched by the hosting provider.

Will WordPress automatic updates fix PHP2Shell?

No. The flaw is in PHP, which runs on your hosting server, not in WordPress itself. Your hosting company needs to apply the patched PHP release.

Which PHP versions fix PHP2Shell?

PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, all released on 21 October 2026. PHP 8.1 and older will not receive an official fix.

How do I check my WordPress PHP version?

In your WordPress dashboard, go to Tools > Site Health > Info, then open the Server section. Your PHP version is listed there.

What if my website is on PHP 8.1 or older?

Your website needs to move to a supported PHP version, ideally 8.3 or higher. Take a full backup first, as older themes and plugins can break when PHP changes.

Can someone fix PHP2Shell for me?

Yes. Ola Digital offers a PHP2Shell security check and fix for $179 + GST. Book your fix here.

Sources