Latest
Luca Bonura · Founder & Editor
Published · Updated

WordPress site or webshop? Ask your host if PHP is patched

For every shop, café, salon or trades business whose website or webshop runs on WordPress or another PHP system: what the "PHP2Shell" flaws are, who has to fix them, and the checks to do now if you have not done them yet.

5 min read
An open laptop on a small shop counter showing a settings page, with a large red padlock on the screen.AI-generated illustration
1
What happened

What did PHP fix on 21 October?

Two critical flaws, and every PHP website needs the fix. On 21 October 2026 the PHP project released PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. They close two flaws, CVE-2026-109618 and CVE-2026-109619, nicknamed "PHP2Shell", that "can allow unauthenticated remote code execution" (PHP). In plain words: someone could run their own code on your web server without a password. PHP is the programming language underneath WordPress, Joomla, Drupal, TYPO3, Magento and many booking plugins. Your site doesn't say "PHP" anywhere, but it still runs on it. The UK's National Cyber Security Centre is clear: "Organisations using any version of PHP are affected and all organisations are highly encouraged to update to the latest fixed version." If that can't happen quickly, "you should consider taking the system offline until it can be fully mitigated" (NCSC). Attackers are using the flaws. On 26 October 2026 the US cyber security agency CISA added both to its list of known exploited vulnerabilities (CISA). Germany's BSI wrote on 22 October that automated attack attempts were under way, but that it knew of no successful attacks on a broad scale.

2
What it means for your business

Who has to fix it: you, your host or your web agency?

That depends on where your website lives. Here's the catch: the fix is not in WordPress, it is one level below, on the server. You rent a hosting package: your host updates PHP. Many did it overnight. WordPress.com wrote on 21 October: "On WordPress.com, security is our job to solve, not yours." (WordPress.com). GoDaddy says it has patched all PHP versions on its Managed Hosting for WordPress, Web Hosting and Windows Hosting, while customers with a VPS must update PHP themselves (GoDaddy). Your job: check your host's status page, or ask. You or your agency run your own server: then nobody patches it for you. You or the agency must install the fixed PHP version. You're on PHP 8.1 or older: the PHP project says these "no longer receive updates", so "contact your vendor for details, or upgrade to a supported version." Updating WordPress won't fix this. Updating PHP will. WordPress.org: "No WordPress update is required or planned for these issues." If your site is built with a website builder, ask the provider whether it is affected.

What you can do this week

What should you do now?

Start with one question to whoever runs your website: "Is PHP on my site patched?" Quick workarounds exist, but the PHP project says they "do not make an installation safe". Only the update does. The short version:

  • ✓Today: find your PHP version. In WordPress go to Tools > Site Health > Info > Server (WordPress.org). On 8.1 or older, book the upgrade with your host or agency.
  • ✓Now: check your host's status page or email them: "Is PHP on my hosting patched against CVE-2026-109618 and CVE-2026-109619?" Also ask whether the setting PHP recommends against the follow-up flaw CVE-2026-115560 is in place.
  • ✓Own server or agency server: install the fix now. The fixed versions are 8.5.12, 8.4.27, 8.3.36 and 8.2.35.
  • ✓Can't patch quickly? Consider taking the site offline until it's fixed, as the NCSC advises. If it stayed online unpatched, ask your web person to check it for signs of a break-in. The NCSC says to "look for backdoors installed by an attacker".
9.2

Severity score (CVSS) of each of the two PHP2Shell flaws

Source: BSI, security notice, version 1.2, 22 October 2026

Common questions

Do I need to update WordPress because of PHP2Shell?

No. WordPress.org says the flaws "are not specific to WordPress and affect any server that hosts a PHP application", and "no WordPress update is required or planned". The fix is a new PHP version on the server. On a hosting package your host installs it; on your own server you or your agency do.

Which PHP version does my website run?

In WordPress you'll find it under Tools > Site Health > Info > Server. Otherwise look in your hosting panel or ask your host. PHP 8.2 and newer have fixed versions (8.2.35 and up). The version number alone is not proof either way: some hosts built the fix into older version numbers, so ask your host to confirm. PHP 8.1 and older no longer get updates from the PHP project, so plan a move to a supported version.

Has my host patched PHP yet?

Check your host's status page or ask support directly. WordPress.com says it handles security for its customers, and GoDaddy says it has patched all PHP versions on its managed and shared hosting. If your host's page only mentions temporary protections, ask when the update follows.

Sources

  1. PHP project, release announcement, 21 October 2026
  2. PHP security advisory GHSA-w8hw-w9fx-j79w on GitHub
  3. PHP security advisory GHSA-6wmf-4rv5-p3rp on GitHub
  4. NCSC, "Critical security issue affecting PHP", 21 October 2026
  5. BSI, BITS-H Nr. 2026-297981-1232, version 1.2, 22 October 2026
  6. CISA, "CISA Adds Two Known Exploited Vulnerabilities to Catalog", 26 October 2026
  7. WordPress.org, "Critical PHP security release", 21 October 2026
  8. Cloudflare blog, 21 October 2026
  9. WordPress.com, 21 October 2026
  10. GoDaddy, "Important PHP security update"
Luca Bonura
Founder & Editor

Luca Bonura started selling online at 17 and funded his first business with 4:30am shifts in a bakery. He built his own product brand, watched it fail, and rebuilt as a freelance performance marketer for everyone from small shops to HelloFresh. Seeing how hard growth is even for people inside the industry, he founded Adlarion. He writes The Small Business Digest in plain English: the news he wished he'd had when starting out.

More from Luca →
The 5-minute Digest

Get the next one in your inbox.

Our newsletter starts soon. No spam, unsubscribe in one click.

We only use your email for the Digest. Privacy