A serious PHP vulnerability was discovered earlier this week. PHP, the software that quietly runs a huge share of the world’s websites. It has been nicknamed PHP2Shell, and it lets an attacker take control of a website’s server without needing a password. If your website runs on WordPress, Joomla, Drupal, Magento or another PHP-based platform, it is worth five minutes of your time today.
Here is what happened in plain English, which websites are at risk, how to check yours, and what makes some websites much safer than others.
What is the PHP vulnerability?
PHP is the programming language underneath many popular website platforms. Most business owners never see it, but it is doing the work every time someone loads a page.
On October 21, 2026, the PHP project released emergency updates for two critical flaws (officially CVE-2026-109618 and CVE-2026-109619). Both let someone on the internet send specially crafted requests to a website and end up running their own code on its server. Once that happens, they can change your pages, steal customer information, or use your site to attack others.
Two details make this worse than the usual security news:
- It affects nearly every version of PHP from the last ten years. Wiz Research, one of the teams that found the flaws, says every version back to PHP 5.4 is affected by at least one of them.
- Your website does not have to do anything wrong. The flaw is in PHP itself, not in your site’s design or content. Wiz notes that even the simplest possible page running on an affected version can be vulnerable.
Why this is a worldwide problem
PHP is not a niche tool. According to W3Techs, it is used by 69.3% of the websites whose server-side language can be identified, and WordPress alone runs 39.6% of all websites. That covers small businesses, online stores, schools and government sites on every continent.
The response has been global too. Patchstack reports that several services went offline as a precaution, including Dutch government websites and major Japanese platforms.
The timing added pressure. According to Huntress, details of the flaws leaked online on October 20, a day before the fix was released. That gave attackers a head start.
Is anyone actually being attacked yet? Reports are early and mixed. Qualys notes that Cloudflare is seeing attack traffic aimed at these flaws, and Patchstack received reports of attacks from hosting companies, while Huntress had not yet seen attacks on its customers’ systems as of October 21. Either way, this is not one to wait on.
Which website builders are at risk?
The question to ask is not “which builder do I use?” but “does my website run on PHP, and has it been updated?”
| Platform | Runs on PHP? | Who needs to update it |
|---|---|---|
| WordPress (including WooCommerce) | Yes | Your host or web developer |
| Joomla | Yes | Your host or web developer |
| Drupal | Yes | Your host or web developer |
| Magento / Adobe Commerce | Yes | Your host or web developer |
| Laravel and other PHP-built sites | Yes | Your web developer |
| Wix | No | Nothing to update |
| Squarespace, Shopify | Run by the platform | The platform |
| Custom sites that do not use PHP | No | Nothing to update |
WordPress websites carry the most risk in practice. WordPress did not cause this, but it is the most popular website platform in the world, so it is where attackers will look first. Researchers have already shown the attack working against WordPress, Drupal and Joomla. And here is the catch most owners miss: the “update” button inside your WordPress dashboard cannot fix this. The fix happens on the server, which is your hosting company’s job or your developer’s.
Older websites are the most exposed. If your site has not been touched in a few years, it may be running a version of PHP that no longer gets official updates. Those sites need more than a quick patch.
Wix is not built on PHP. Wix’s own engineering team describes a platform made of about 2,000 services written in Scala, Java and Node.js, and Wix site owners never manage a server. There is nothing for a Wix site owner to update for this flaw.
Squarespace and Shopify run the servers for you. You do not manage a server on either, so there is nothing for you to update; the platform is responsible. As of October 22, we have not seen a public statement from either about PHP2Shell, so it is worth keeping an eye on their announcements.
How to check if your website is at risk
You do not need to be technical to do this. Send your hosting company or web developer this message:
“Is our website running on PHP? If so, has it been updated for the PHP2Shell vulnerability (CVE-2026-109618 and CVE-2026-109619)?”
A good host will give you a clear yes or no. Then:
- If the answer is yes and it has been updated, you are in good shape. Ask whether any old copies of your site, like a test site or an old version on a subdomain, were updated too.
- If the answer is “not yet,” ask when. PHP’s own guidance is that updating is the only complete fix.
- If no one can answer, that is the real problem. It is worth finding out who controls your website’s hosting before something goes wrong.
- Do not install “security fix” plugins that promise to solve this. Patchstack warns against them. This cannot be fixed from inside your website’s dashboard.
- If your site takes payments or stores customer details and cannot be updated quickly, consider putting it in maintenance mode until it is.
What makes a website safer
No website is 100% safe, and anyone who promises that is overselling. But some websites are much less exposed than others, and PHP2Shell shows why.
Fewer moving parts means fewer ways in. A typical WordPress site is built from the core software, a theme, a page builder and often a dozen or more plugins, each made by a different company on its own update schedule. Each one is another thing that can go wrong. Earlier this month, a WordPress plugin called Bricksforge had a maximum-severity flaw that was attacked in the wild. A site built only from what it needs has less to break.
Not running PHP takes this flaw off the table entirely. Many modern custom websites are built ahead of time and served as finished pages, without PHP running behind them. A site built this way has nothing to patch for PHP2Shell. That does not make it immune to every risk, but it does make it unaffected by this one and by the next PHP emergency too.
Being one of millions makes you a target. Attackers like problems like this because one attack works on a huge number of websites at once. A site built on a less common foundation is not part of that crowd.
Knowing who is responsible matters most. Whether your site is on WordPress, Wix or something custom, the safest websites are the ones where someone clearly owns updates and can answer the question “are we affected?” within a day.
Not sure if your site is affected?
Is your website affected?
If you are reading this because a client, a partner or your own nerves asked “are we OK?”, the fastest way to know is to ask your host the question above.
If you would rather have someone look for you, our free marketing audit includes a check of what your website runs on and whether it looks up to date, along with its speed and how it shows up on Google. It is a written review with no pitch attached, and it is free whether your site is on WordPress, Wix or anything else.