Skip to main content

How one PHP flaw left your WordPress site open to attack for over 20 years

Published

PHP logo on top of a laptop executing php code

Just after midnight on 22 October 2026, the team that maintains PHP released an emergency update for two flaws—rated 9.2 out of 10 for severity.

Both allowed a stranger on the internet to run their own code on a web server without logging in to anything (known as remote code execution, or RCE). The security community named the pair PHP2Shell, and if your business website runs on WordPress, your site was built with these vulnerabilities included.

PHP is the server-side code behind WordPress. Every time a customer opens a page on a WordPress site, the server executes PHP code to assemble that page on the spot. You never see it, and there is no setting for it in your WordPress dashboard. It is installed and updated by your hosting company, and the same engine sits under a huge share of the websites on the internet, such as Facebook (though they have their own version now) and Wikipedia.

PHP's own advisory (opens in a new tab) says that on a common server setup, an attacker's request could trigger the attack before any WordPress code had run. Your security plugin and your login screen never got a chance to intervene.

Hosting platform Laravel Forge notes (opens in a new tab) they affect PHP versions dating back to 2004, so an older site offered no protection.

Your website's security is only as strong as the layers underneath it that you don't control, and WordPress puts several of those layers between you and your customers. For most businesses, the safer website is one with no such engine sitting on a public server waiting to be attacked.

What is PHP2Shell, in plain English?

Think of PHP as the receptionist at a busy office. Every visitor, meaning each person who loads a page on your site, hands over a form, and the receptionist processes it before the office acts on it. PHP2Shell was two ways of confusing that receptionist.

The first vulnerability, CVE-2026-109618 (opens in a new tab), comes into play when PHP runs out of memory halfway through reading a request. An attacker could send a deliberately messy upload that pushed PHP over its limit and left its paperwork half finished. The cleanup that followed treated that half-finished paperwork as valid, which gave the attacker a way to slip in instructions of their own.

The second, CVE-2026-109619 (opens in a new tab), is about leftovers. PHP could hold on to a reference to one visitor's data after throwing that data away, and the next request handled by the same worker could pick it up before the slate was wiped. An attacker who controlled both requests could use that gap to run code on the server.

Running code on the server means the attacker gets to act as your website. That opens the door to rewriting your pages, planting hidden spam links that drag down your Google rankings, redirecting your visitors to scam sites or reading whatever the server can see. Security firm Qualys also reported (opens in a new tab) that researchers could pull fragments of server memory, which can hold passwords and access keys. PHP also handles database requests, meaning—if you store customer data or proprietary business information on your servers—attackers could potentially steal this data and use or distribute it. This is the most potentially disastrous and dangerous avenue for your business.

Why one update exposed every WordPress site at once

A WordPress site is a stack of shared parts. Your theme and plugins run on WordPress, and WordPress runs PHP on a server your host manages. When a flaw turns up in a shared layer, it lands on every site using that layer on the same morning. You don't need to be a target. You only need to be on the list of sites running the software.

The fix isn't yours to apply either. PHP updates come from the host, and hosts move at different speeds. mySites.guru (opens in a new tab), which monitors a large number of live WordPress and Joomla sites, found that 17 minutes after the advisories went public, fewer than one in a thousand of those sites reported a patched version.

For a sizeable group, no fix is coming at all. The patched releases cover PHP 8.2 through 8.5. Sites on PHP 8.1 or older get no official update, and mySites.guru found that 18% of the WordPress sites it monitors run one of those older versions. WordPress allows this on purpose: its current release still lists PHP 7.4 as compatible (opens in a new tab), even though PHP stopped supporting 7.4 (opens in a new tab) in November 2022. Nothing in WordPress pushes an old site forward, so many sit on an outdated engine until something like PHP2Shell arrives.

Where WordPress leaves you holding the risk

WordPress became popular because it made websites easy to start. The trade is that you take on a moving system you have to keep alive. Plugins need updating, and each one is written by a different developer with their own standards and their own timeline. PHP needs updating too, by someone else, on their schedule. Every one of those is a door, and you are responsible for whatever comes through it.

Most small business owners never signed up for that job. You wanted a site that brings in enquiries, and you ended up with software that needs a caretaker. When the caretaker misses a week, your business carries the consequences. A hacked site can be flagged by Google with a warning in search results, and that costs you enquiries long after the cleanup is done.

PHP2Shell shows the limit of the usual WordPress advice. Keeping plugins updated and installing a security plugin are sensible habits, but neither would have stopped an attack that runs before WordPress loads.

How a custom-built site avoids the problem

At Liquid Lava we build sites differently. Each page is generated ahead of time as a finished file and served from Cloudflare's global network, close to wherever your customer is. On the morning PHP2Shell broke, our sites had nothing to patch.

You still edit your own content. Your text, photos, videos and policies are changed through a clean dashboard. When you publish a change, the site rebuilds itself with the new content. The editing tools stay off your public website, so the place your customers visit gives an attacker very little to work with.

No website is immune to every risk, and we don't pretend otherwise. Domains and accounts still need care, which is what our monthly management covers. The difference is the size of the target. A site made of finished files has a far smaller surface to attack than a server that runs code for every visitor.

The same approach makes your site faster. Finished files load quickly from a nearby server, which helps your Google Core Web Vitals scores and keeps impatient mobile visitors on the page. You also stop paying for plugin licences and security add-ons that exist mainly to keep WordPress standing.

What to do this week

If your site runs on WordPress, log in to your hosting control panel and find the PHP version setting. The patched versions are 8.2.35, 8.3.36, 8.4.27 and 8.5.12. Some panels only show the main number, such as 8.3, so email your host and ask directly whether the patched release is installed on your server. If your site is on PHP 8.1 or older, no patch is coming, and you need to plan a move to a newer version with whoever looks after your site, testing your theme and plugins as you go.

Then use the scare to ask a bigger question: how much time and money does your website take to keep safe each year, and who is doing that work?

If you can't answer that with confidence, it may be time for a site that doesn't need the same caretaking. Book a free 30-minute discovery call with us, and we'll look at your current site and walk you through what a move would involve.

Stay vigilant.

More guides for business owners

Ensure your business' security.

Book your free discovery call and see how we can help you stay secure.

Book a free discovery call