HackSpotby Amethyst Apps
How it worksWhat we checkPricingGuidesInsightsAbout
Log inCheck my website
HackSpot / Insights

Is my WordPress site affected by PHP2Shell?

PHP2Shell is a PHP flaw, not a WordPress bug, so updating WordPress won't fix it. How to tell if your site is at risk and what to ask your host.

By HackSpot team (Amethyst Apps) · October 23, 2026 · 4 min read

HackSpot: is my WordPress site affected by PHP2Shell?

The short version: PHP2Shell is a flaw in PHP itself, the language WordPress runs on. It isn't a WordPress or plugin bug, so updating WordPress doesn't fix it. What matters is which PHP version your host runs and whether it has the 21 October 2026 fixes. Check what your site shows for free, then ask your host to confirm.

Why WordPress sites are in scope

On 21 October 2026 the PHP project fixed two critical flaws, CVE-2026-109618 and CVE-2026-109619, rated 9.2 out of 10. The PHP advisory says the risk covers all PHP installations serving web requests, whichever way PHP is connected to the web server (PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed are all named). The researchers who found the flaws, at Wiz, reported confirming unauthenticated remote code execution against WordPress and Drupal while testing.

According to the advisories, the attack doesn't depend on a bug in your site's own code. That's why a fully up-to-date WordPress site with well-kept plugins can still be at risk if the PHP underneath it hasn't been updated.

Who fixes what

Part of your siteWho usually updates itDoes it fix PHP2Shell?
PHPYour web host (or whoever manages your server)Yes, this is the fix
WordPress coreYou, your developer or automatic updatesNo
Plugins and themesYou or your developerNo
WooCommerceYou or your developerNo

If you're on shared or managed WordPress hosting, your host controls PHP. If you have your own server (a VPS), whoever looks after it needs to update PHP and restart it.

What to do this week if you run WordPress

  1. Check your PHP version. In your WordPress dashboard go to Tools > Site Health > Info and open Server. It shows the PHP version your site runs. You can also run a free HackSpot check to see what your site shows the outside world.
  2. Compare it with the fixed releases. The fixes are in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 (and newer releases in each branch). PHP 8.1 and older don't get new releases from the PHP project.
  3. Ask your host to confirm. An older number doesn't prove you're unpatched, because many hosts patch without changing the number. Send our copy-and-paste email to your web host.
  4. If you're on PHP 8.1 or older, plan a move. WordPress recommends PHP 8.3 or newer and warns that end-of-life versions may expose your site to security vulnerabilities. Test on a staging copy first if your host offers one.
  5. Keep WordPress, plugins and themes up to date anyway. It doesn't fix PHP2Shell, but it closes other doors.

Should I install a "PHP2Shell security plugin"?

Be careful. A plugin can't update the PHP your host runs. The PHP project says only updating is a complete fix; temporary configuration changes reduce some attack paths but don't make an installation safe, and they're server settings your host controls. Treat emails or ads offering a "PHP2Shell patch plugin" with suspicion: see PHP2Shell phishing and fake patch offers.

If you think your site was attacked

Signs worth reporting to your host include unexplained new admin users, files you didn't add, your host warning about malware or spam, or the site suddenly sending visitors elsewhere. Ask your host to check, and change your WordPress, hosting and email passwords. The UK's NCSC suggests using an assured incident response provider if you don't have the skills in-house.

Questions people ask

Does updating WordPress fix PHP2Shell?

No. PHP2Shell is in PHP, which your host installs and updates. Updating WordPress, plugins or themes doesn't change the PHP version.

Which PHP version does WordPress recommend?

WordPress.org recommends PHP 8.3 or newer. WordPress also works on PHP 7.4 and later, but WordPress warns that end-of-life versions may expose your site to security vulnerabilities.

Is WooCommerce affected?

WooCommerce runs on WordPress, which runs on PHP, so the same answer applies: the fix is your host updating PHP.

My host says it's handled. How do I know?

Ask them to confirm in writing which PHP release your site runs, or that their package includes the fixes for CVE-2026-109618 and CVE-2026-109619, and that PHP was restarted afterwards.

Can HackSpot tell if my WordPress site is patched?

Not for certain, and we don't pretend to. HackSpot shows what your site reveals publicly, such as the PHP version if it's on show, and says "looks unpatched, ask your host" when an older version appears.

More on PHP2Shell

  • PHP2Shell: what small businesses need to do today
  • How to check which PHP version your website runs
  • How to update PHP in cPanel and Plesk
  • Old WordPress versions (guide)

Sources

  • PHP security advisory, 21 October 2026 (php.net)
  • GitHub security advisory GHSA-6wmf-4rv5-p3rp, CVE-2026-109619 (PHP project)
  • PHP2Shell research (Wiz)
  • WordPress requirements (WordPress.org)
  • Site Health screen (WordPress documentation)
  • Critical security issue affecting PHP (NCSC)

Check your website free

See what your website shows the world in about a minute: a plain-language report, who should fix each thing, and a message to send them.

Check my website

Free to check

See what your website shows the world.

Check my website free
HackSpotby Amethyst Apps

Plain-language security checks for your website and the suppliers your business depends on.

HackSpot

  • How it works
  • What we check
  • Free check
  • Pricing

Resources

  • Guides
  • Insights
  • Supplier status

Help

  • About
  • Security
  • Contact us

Amethyst Apps

  • All apps
  • IndexStream
  • Partners

© 2026 Amethyst Apps. Built in the UK.

2G, Ingram House, 227 Ingram Street, Glasgow, G1 1DA, United Kingdom

PrivacyTermsCookiesSecuritySitemapPartners
EnglishEspañolFrançaisDeutschItalianoPortuguêsNederlandsPolskiSvenska日本語
HackSpot