Godin Digital
← Back to Blog

PHP2Shell: Is Your WordPress Site Affected? A Plain-English Check

November 14, 2026
6 min read

In October, PHP fixed two serious security flaws. PHP is the software that runs WordPress, so if your business site is on WordPress, this one is worth ten minutes. Here's what happened, how to check your site, and the email to send your host.

Quick take

Updating WordPress doesn't fix this. The fix is on the server, and on most business sites that means your host. Check your PHP version, then ask your host to confirm in writing that the patch is in. No sign of mass hacking so far, so no need to panic, but don't leave it.

What happened

On 21 October 2026 the PHP team released fixes for two critical flaws, CVE-2026-109618 and CVE-2026-109619, nicknamed PHP2Shell. Both are rated 9.2 out of 10. In plain words: on a server running an unpatched PHP, an attacker could make it run their own code, without logging in to anything. From there they could change your pages, plant spam links or read what your forms collect.

Five days later, the US cybersecurity agency CISA added both flaws to its list of vulnerabilities being exploited by attackers. On WordPress, the picture is calmer: as of 28 October, the Wordfence team had logged more than 77,000 attack attempts but had not seen one WordPress site taken over this way.

The catch is where the fix lives. The flaws are in PHP, not in WordPress, so WordPress's security team had nothing to release. A site with every plugin up to date is still exposed if the PHP under it isn't patched.

Check your site in four steps

  1. 1. Find out what your site runs on

    If you log in at yoursite.com.au/wp-admin, it's WordPress. Another sign: right-click an image on your site, copy its address, and look for /wp-content/ in it. WooCommerce, Joomla and Drupal also run on PHP. Wix, Squarespace and Shopify don't need anything from you: the platform runs the servers and patches them.

  2. 2. Check your PHP version

    In WordPress, go to Tools > Site Health > Info > Server. The PHP version is listed there. Your hosting control panel (cPanel, Plesk) usually shows it too.

  3. 3. Compare it with the fixed versions

    The fixed releases are 8.5.12, 8.4.27, 8.3.36 and 8.2.35, or anything newer in the same line. PHP 8.1, 8.0 and 7.4 are out of support: the PHP team published a patch for them, but your host has to apply it by hand. If you're on one of those, ask.

  4. 4. Ask your host to confirm in writing

    The version number alone isn't the whole answer. Hosts that patch an old version themselves don't always change the number, and the fix only takes effect once PHP is restarted. A two-line email settles it (below).

Fixed versions: 8.5.12, 8.4.27, 8.3.36, 8.2.35, or newer.

The email to send your host

Copy it, change the web address, send it to your hosting support.

Hi,

Can you confirm the PHP running my site (yoursite.com.au) includes the fixes for CVE-2026-109618 and CVE-2026-109619 (PHP2Shell), released on 21 October 2026, and that PHP was restarted after the update?

Thanks

If a developer or agency manages your site, send it to them instead. Keep the reply: if something goes wrong later, it shows you asked.

Why the sites I build weren't affected

I don't build on WordPress or on website builders. Every site I make is custom coded, in JavaScript with Next.js. There is no PHP anywhere in them, so PHP2Shell had nothing to attack.

A brochure site I build is generated ahead of time: visitors get ready-made pages, with no PHP and no database behind them. This site works the same way. Sites that need more, like the MAP Group store with its online payments and customer accounts, run on Vercel, which patches its own servers. Keeping the site's code up to date is my part, and it's included in the $100 a year maintenance.

To be straight with you: no website is immune. In December 2025, React and Next.js had a critical flaw of their own, nicknamed React2Shell. It hit sites that run code on the server for each visitor, and they had to update fast. A pre-built brochure site had nothing exposed. The lesson is the same as with PHP2Shell: the less a site runs on its server, the less there is to attack, and someone has to be responsible for updates.

Should you leave WordPress over this?

No, not over this alone. If your host confirms the patch, you're done. Plenty of WordPress sites are well run and safe.

It's worth thinking about a rebuild when the check above turned up other problems: a PHP version your host stopped supporting, plugins nobody has updated in years, a site that's slow on phones, or nobody you can call when something breaks. That's when the yearly cost of keeping WordPress safe starts to add up. I've compared the options in custom coded website vs website builder and what website maintenance really costs.

Questions

Not sure what your site runs on?

Send me your web address. I'll tell you what it's built with and who you need to ask, free.