Skip to content
Skip to content
Digitalized Planet

PHP2Shell: what the October 2026 PHP vulnerability means for your website

On 21 October 2026 PHP fixed two critical flaws that can let a stranger run code on a web server without logging in. If your site runs on PHP, as WordPress, WooCommerce, Joomla, Drupal, PrestaShop and Magento do, here is what to do.

USD 750 once, USD 79 a month. No PHP, no plugins, nothing for you to update.

Last updated October 22, 2026

What happened

On 21 October 2026 the PHP project published a security advisory and released PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. They fix two vulnerabilities, CVE-2026-109618 and CVE-2026-109619, that allow unauthenticated remote code execution: someone who is not logged in can make the server run code of their choosing. Security researchers call the pair PHP2Shell; PHP itself does not use that name.

PHP's own advisories on GitHub rate both critical, 9.2 out of 10 (CVSS 4.0). The first, "RCE via OOM corruption", abuses the moment PHP runs out of memory while reading a request. The second, "RCE via stale global state", abuses data one request leaves behind for the next request handled by the same server process.

Who is at risk

PHP says every PHP installation that serves web requests is at risk: PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed. It rates the risk highest for Apache with mod_php, where it has demonstrated an attack in which a single request from someone not logged in triggers it before any of the site's own code runs.

So the flaw is in PHP itself, not in WordPress or a plugin. Updating WordPress, your theme or your plugins does not fix it. What fixes it is the PHP on the server, and on most small business sites that is your hosting company's job.

Which PHP versions are fixed

  • Fixed: PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, and anything newer in the same line.
  • PHP 8.1, 8.0, 7.4 and older get no more updates from the PHP project. Given the severity, PHP published small source fixes for 7.4, 8.0 and 8.1 for people who build PHP themselves, and some Linux distributions and long-term support vendors ship their own fixes.
  • Linux distributions received the patches in advance, so a server whose packages are kept current may carry the fix under an older-looking version number. Only your host can tell you for sure.

What to do today

  1. Find your PHP version: in your hosting control panel (cPanel, Plesk or your host's own), or in WordPress under Tools, Site Health, Info, Server. The 5-minute check.
  2. Ask your host in writing: "Is the PHP on my site patched against CVE-2026-109618 and CVE-2026-109619, and since when?" Keep the answer.
  3. If you run your own server, update PHP now. How to update PHP also lists the temporary settings PHP gives for servers that cannot update at once.
  4. Make a fresh backup of the files and the database, and keep it off the server.
  5. Over the next weeks, watch for signs of a break-in: admin users you did not create, files you did not upload, pages that send visitors to spam or casino sites, or Google's "This site may be hacked". What to do if it happens.

What it does not mean

It does not mean every WordPress site has been hacked, or that WordPress has a new hole of its own. Many hosts update PHP for all their customers, and a patched server is not exposed to these two flaws. The sites most at risk are the ones nobody looks after: old PHP versions, servers set up years ago and never touched, sites whose builder is gone. Is WordPress still safe?

Why small business sites are the ones exposed

The typical small business site is WordPress or a similar system on shared hosting, with a theme and several plugins. PHP, the system, the theme and each plugin all need security updates for as long as the site is online. Once a flaw is public, attackers scan the web for servers that still run the old version, and a site nobody updates is exactly what they find.

A site with nothing to update

If you would rather never think about PHP versions again, a site can be built without PHP, plugins or a database behind its pages. That is how we build ours: a website without maintenance.

This page will change

We update this page as PHP, Linux distributions and hosts publish more. The date at the top is the last time we checked it against PHP's advisory.

Done with PHP updates?

We rebuild your site as fast pages with nothing on the server for you to patch, and you still edit it from your phone.

Rebuild my website

Written with AI help; facts from php.net, github.com; checked October 22, 2026.