Is Your WordPress Site Exposed to PHP2Shell? What to Do This Week

PHP2Shell is a PHP flaw, not a WordPress one, but it reaches every WordPress site. A third run PHP versions with no official fix. What to ask your host.

· Updated October 29, 2026 · 8 min read

Updated October 29, 2026. Since this piece first ran on October 22, CISA, the US government’s cybersecurity agency, has added both flaws to its list of vulnerabilities attackers are known to exploit, and researchers have confirmed working attacks against unpatched PHP. The fix is unchanged. One step is new: after the update, PHP has to be restarted, or the server keeps running the old code.

On October 21, 2026, the PHP project shipped emergency fixes for two critical flaws in PHP itself, now known as PHP2Shell. Both can let an attacker run code on a web server without logging in. 1 Source 1 PHP Group, security advisory, October 21, 2026. CVE-2026-109618 and CVE-2026-109619, both rated CVSS v4.0 9.2.

WordPress didn’t cause this. WordPress can’t fix it either. The flaw sits one layer down, in the language every WordPress site runs on, which makes it a question about who looks after your server.

Is WordPress affected by PHP2Shell?

Yes, indirectly. Every WordPress site runs on PHP, so a site on an unpatched PHP version is at risk however current its WordPress core and plugins are. A WordPress update won’t help. The fix is a newer PHP on the server: 8.5.12, 8.4.27, 8.3.36 or 8.2.35.

How much risk depends on how the server runs PHP. The PHP project rates it highest for servers running Apache with mod_php. Other common setups are affected too, so the advice is the same everywhere: update. 2 Source 2 PHP Group, October 21, 2026. One advisory notes no complete exploit has been shown on PHP-FPM, another common setup; the other reports its attack path validated on both mod_php and PHP-FPM.

The harder number is how many sites can’t simply take that update. Here is how the sites that report to WordPress.org’s update service break down, as of October 29: 3 Source 3 WordPress.org PHP version statistics, read October 29, 2026. Covers every reporting site, including small and inactive ones. A week earlier, 64.1% ran 8.2 or newer.

PHP version your site runsShare of reporting WordPress sitesWhat the PHP project offers
8.2 and newer66.8%Official fixed release
7.4 to 8.127.8%No release; source backports only
5.4 to 7.35.1%Nothing; end of life

Fix status is from the PHP advisory and Tenable’s summary of it. 4 Source 4 Tenable, October 21, 2026, citing Calif’s finding that the earliest affected code path dates to PHP 5.4.0, and listing 7.4 to 8.1 as source backports only and 5.4 to 7.3 as end of life with no fix.

Roughly one in three of those sites runs a PHP version that no official PHP release fixes. For those sites, “just update” means moving up a version. Your host, your Linux distribution or a long-term support vendor may have backported the fix for you. The PHP project published source backports for 7.4 to 8.1 and tells anyone on those versions to ask their vendor or upgrade. 5 Source 5 PHP Group, October 21, 2026: “PHP 8.1 and older no longer receive updates from the PHP project.” Minimal source backports were published for 7.4, 8.0 and 8.1. PHP 8.2 reaches end of life on December 31, 2026. WordPress itself recommends PHP 8.3 or newer and treats 7.4 as a legacy floor. 6 Source 6 WordPress.org Requirements, read October 22, 2026: “PHP version 8.3 or greater” recommended; 7.4+ works in legacy environments.

One more date matters. PHP 8.2 itself stops getting security fixes on December 31, 2026. A site that patches to 8.2 now buys itself until the end of the year, and then faces the same question again.

How serious is it?

Serious enough that the details didn’t wait for the fix. The CVE numbers leaked on October 20, and the PHP project moved its release up a day. 7 Source 7 Tenable, October 21, 2026. The PHP project’s pre-announcement went out October 20; the release was first planned for October 22.

The reports so far:

  • Amazon Threat Intelligence logged an attempt against its honeypots on October 17, four days before public disclosure, and more on October 21. It says it is unclear whether those attempts would have worked against real systems, and that PHP2Shell is now seeing broad exploitation attempts in the wild. 8 Source 8 Amazon Threat Intelligence, AWS Security Blog, October 21, 2026.
  • watchTowr reports exploitation in the wild as of October 21. 9 Source 9 watchTowr FAQ, updated October 22, 2026.
  • At release, PHP’s security team had found no working exploit among the proof-of-concepts circulating, according to Tenable. 10 Source 10 GitHub advisories GHSA-w8hw-w9fx-j79w and GHSA-6wmf-4rv5-p3rp, October 21, 2026; Tenable, October 21, 2026. That changed within days. On October 24 a researcher reported successfully exploiting three honeypot servers running unpatched PHP 8.4, and on October 26 Trail of Bits confirmed working exploits against unpatched PHP 8.2 to 8.5. 11 Source 11 Tenable, php2shell FAQ, updated October 28, 2026, reporting Adel Karimi (October 24) and Trail of Bits (October 26).
  • On October 26, CISA added both flaws to its Known Exploited Vulnerabilities catalog, the US government’s list of flaws attackers are using, and gave federal agencies three days to act. 12 Source 12 CISA, Known Exploited Vulnerabilities Catalog: both CVEs added October 26, 2026, due October 29, 2026.

As of October 28, Tenable knew of one reported compromise, a campaign against firewall appliances rather than websites, which it had not been able to confirm. Researchers at Calif, one of the teams credited with finding the flaws, also showed they could be used to run code on specific versions of popular PHP applications without logging in, WordPress among them. 13 Source 13 Tenable, October 21, 2026. A research finding about exploitability, not a report of attacks. The specific WordPress versions were not named. If you’re checking whether you were hit, Amazon’s advice is to start from October 17.

A site that patches to 8.2 now buys itself until the end of the year, and then faces the same question again.

What to do this week

None of this needs a developer to start. It needs someone to ask the right questions of whoever runs your server.

  1. Find your PHP version. In the WordPress dashboard, go to Tools, then Site Health, then the Info tab, and open the Server section. Write the version down. A number below the fixed releases doesn’t always mean you’re unpatched, because Linux distributions often backport security fixes without changing the version number. Treat it as the starting point for the next step.

  2. Ask your host three things, in writing:

    • Is the PHP2Shell fix applied on the server my site runs on, in which package or version, and has PHP been restarted since?
    • If my site is on PHP 8.1 or older, where is the fix coming from, and when?
    • Will you check the server logs back to October 17 and tell me what you find?

    The restart matters. Installing the updated packages doesn’t protect PHP processes that are already running, so until PHP restarts, the server can still be running the old code. 14 Source 14 Tenable, php2shell FAQ, updated October 28, 2026: restart PHP services after updating. Google Cloud advises capturing worker memory on any server showing signs of probing first, because a restart erases that evidence. A good managed WordPress host should answer all three the same day. A budget shared host may tell you to pick a newer PHP version from your control panel yourself. If your site is on a server your team or a freelancer set up, the answer to all three is “us”, and the work starts now.

  3. If something breaks after the update, fix forward. PHP has confirmed a bug in 8.4.27 and 8.5.12 that can crash some code that reads XML, and the fix had not shipped as of October 26. 15 Source 15 Tenable, php2shell FAQ, updated October 28, 2026: a confirmed regression in PHP 8.4.27 and 8.5.12 that can crash some SimpleXML applications; fix merged, not yet released as of October 26. If a plugin stops working, have your host or developer deal with that plugin rather than rolling PHP back to an unpatched version.

  4. If you’re on PHP 8.1 or older, book the upgrade this week and do it properly. Moving up a version can break old plugins and themes, so test on a staging copy first, update or replace whatever fails, then switch production. A plugin that can’t run on current PHP was already a liability.

  5. Treat a security plugin or firewall as a stopgap. The PHP project says there are no complete mitigations and updating is the only safe choice. Its own interim server settings block specific attack paths but, in its words, “do not make an installation safe.” 16 Source 16 PHP Group, October 21, 2026, “If you cannot update immediately.” The interim settings are server-level and need a host or administrator to apply them. A firewall can buy time while the update happens. Separately, on October 23 the PHP project flagged a narrower issue in a feature called session upload progress, which affects only applications that change their session settings while running, and suggested switching that feature off until its next bugfix release where it applies. 17 Source 17 PHP Group, “Informational advisory: Session upload progress,” October 23, 2026 (CVE-2026-115560): “Applications that never change the serialize handler at runtime can keep the feature enabled.” Your host or developer can tell you whether it does.

What the scramble actually tells you

If you can name your plugins but not the person who keeps PHP current underneath them, or how fast they move, PHP2Shell just showed you the gap.

The question of who owns that layer is worth settling now, while it’s urgent, because the answer pays off well past this CVE. A site with a named owner for every layer, a patch commitment in the hosting contract and a plugin stack known to run on current PHP can take a runtime upgrade as routine maintenance. That’s the difference between reading about the next PHP2Shell and losing a week to it.

If this week showed you that nobody clearly owns that layer, that is a decision worth making on purpose. For some companies the answer is a better host or a clearer contract. For others it’s a hard look at whether the platform still fits. The real cost of WordPress at mid-market scale puts numbers on the upkeep, and 11,334 new vulnerabilities in a year covers the plugin side of the same risk. If you’re weighing a bigger change, the six-factor evaluation and the WordPress Score will tell you whether moving makes sense for you, or whether staying is the better call.

The research is free. So is the diagnosis. 60 seconds →

Notes & Sources

1Source: PHP Group, security advisory, October 21, 2026, and pre-announcement, October 20, 2026. PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 fix two critical vulnerabilities, CVE-2026-109618 (RCE via OOM corruption) and CVE-2026-109619 (RCE via stale global state); the CVSS v4.0 score of 9.2 for both is given in the October 20 pre-announcement. php.net/archive/2026.php
2Source: PHP Group, security advisory, October 21, 2026: all PHP installations serving web requests are at risk, highest for mod_php. GitHub advisory GHSA-w8hw-w9fx-j79w (CVE-2026-109618) notes no complete PHP-FPM exploit has been demonstrated; GHSA-6wmf-4rv5-p3rp (CVE-2026-109619) reports its session path validated against both mod_php and PHP-FPM.
3Source: WordPress.org PHP version statistics, read October 29, 2026 (api.wordpress.org/stats/php/1.0/). PHP 8.2 and newer: 66.8% of reporting sites (8.6, a test release, is 0.03%). PHP 7.4 to 8.1: 27.8%. PHP 5.4 to 7.3: 5.1%. Below 5.4: 0.4%. On October 22 the split was 64.1%, 30.2%, 5.3% and 0.4%. Covers every site that reports to WordPress.org's update service, including small and inactive ones.
4Source: Tenable, Satnam Narang, 'php2shell (CVE-2026-109618, CVE-2026-109619): Frequently Asked Questions About Critical PHP Remote Code Execution Vulnerabilities,' October 21, 2026. Cites Calif's writeup that the earliest affected code path dates to PHP 5.4.0, and its fixed-version table: 7.4 to 8.1 have no official release (minimal source backports), 5.4 to 7.3 are end of life with no fix.
5Source: PHP Group, security advisory, October 21, 2026. 'PHP 8.1 and older no longer receive updates from the PHP project.' Minimal source backports were published for PHP 7.4, 8.0 and 8.1. Linux distributions and LTS vendors received the patches in advance. The PHP 8.2.35 release notice adds that PHP 8.2 reaches end of life on December 31, 2026.
6Source: WordPress.org, Requirements page, read October 22, 2026. Recommends PHP 8.3 or greater; WordPress also works with PHP 7.4+ in legacy environments, which the page notes have reached end of life. wordpress.org/about/requirements/
7Source: Tenable, October 21, 2026: the CVE identifiers circulated on Hacker News and social media on October 20, and the release, first planned for October 22, was moved up a day. The PHP project's pre-announcement went out October 20.
8Source: Amazon Threat Intelligence, 'Amazon Threat Intelligence identifies PHP2Shell exploitation prior to public disclosure in MadPot,' AWS Security Blog, October 21, 2026. An attempt dating to October 17 in MadPot honeypot telemetry, more attempts on October 21; unclear whether they would have succeeded against real-world systems; "PHP2Shell is now seeing broad exploitation attempts in the wild"; investigate from October 17 at the latest.
9Source: watchTowr, 'Frequently Asked Questions About PHP Remote Code Execution (PHP2Shell CVE-2026-109618 & CVE-2026-109619),' published October 20, updated October 22, 2026. Exploitation observed in the wild as of October 21 through its honeypot network.
10Source: GitHub security advisories GHSA-w8hw-w9fx-j79w and GHSA-6wmf-4rv5-p3rp (php/php-src), October 21, 2026: both describe validated remote code execution; neither states exploitation in the wild. Tenable, October 21, 2026: PHP's security team found no functional exploits among the proof-of-concepts at release, and no confirmed successful compromise is reported.
11Source: Tenable, php2shell FAQ, updated October 28, 2026: Adel Karimi reported successful exploitation of three honeypot servers running PHP 8.4.26 (October 24); Trail of Bits said it confirmed the exploits work against pre-patch PHP 8.2 through 8.5 releases (October 26); Dream Research reported a campaign against 24 internet-facing firewall appliances (October 26), which Tenable had not independently confirmed. Tenable has not verified any circulating public exploit code itself.
12Source: CISA, Known Exploited Vulnerabilities Catalog: CVE-2026-109618, 'PHP Memory Corruption Vulnerability,' and CVE-2026-109619, 'PHP Stale Internal Request-State Vulnerability,' both added October 26, 2026, with a due date of October 29, 2026 for US federal civilian agencies. Read October 29, 2026.
13Source: Tenable, October 21, 2026: Calif 'confirmed pre-authentication remote code execution against specific versions of popular PHP applications, including WordPress', Drupal, Joomla and Magento among them. A research finding about exploitability, not a report of attacks; the specific WordPress versions were not named. The PHP Foundation credits Calif, OpenAI and Wiz, among others, for the research and disclosure.
14Source: Tenable, php2shell FAQ, updated October 28, 2026: installing updated PHP packages does not patch processes that are already running; restart PHP services after updating. Google Cloud advises capturing worker memory on servers that show signs of probing before restarting, because a restart erases that evidence.
15Source: Tenable, php2shell FAQ, updated October 28, 2026: PHP confirmed a regression in PHP 8.4.27 and 8.5.12 that can crash some SimpleXML applications; a fix was merged but had not shipped as of October 26.
16Source: PHP Group, security advisory, October 21, 2026, 'If you cannot update immediately.' Interim settings, including disabling session upload progress, block specific confirmed paths but 'do not make an installation safe.' They are server-level and need a host or administrator to apply them.
17Source: PHP Group, 'Informational advisory: Session upload progress,' October 23, 2026 (CVE-2026-115560): applies only where an application changes session.serialize_handler at runtime; PHP suggests setting session.upload_progress.enabled=0 'until the next regular bugfix release'; 'Applications that never change the serialize handler at runtime can keep the feature enabled.' php.net/archive/2026.php

Frequently asked questions

Indirectly. Both flaws, known as PHP2Shell, are in PHP itself, not in WordPress core or plugins. Because WordPress runs on PHP, any WordPress site on an unpatched PHP version is at risk. The PHP project rates both critical (CVSS v4.0 9.2), says they can allow unauthenticated remote code execution, and considers the risk highest on servers running Apache with mod_php. The fix is a PHP update on the server, not a WordPress update.
PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, released October 21, 2026. PHP 8.1 and older get no official release; the PHP project published minimal source backports for 7.4, 8.0 and 8.1, and some Linux distributions and long-term support vendors ship their own patched packages. According to Tenable, versions 5.4 through 7.3 have no fix from the PHP project.
Not completely. The PHP project states there are no complete mitigations and that updating is the only safe choice. Its interim server settings reduce exposure to specific attack paths but, in its words, do not make an installation safe. A firewall may block known attack patterns while the update happens, but the flaw sits below WordPress, where a WordPress plugin cannot reach it.
In the WordPress dashboard, open Tools, then Site Health, then the Info tab, and expand the Server section. It shows the PHP version. A version number below 8.2.35, 8.3.36, 8.4.27 or 8.5.12 does not always mean unpatched, because Linux distributions often backport fixes without changing the version number, so confirm with your host. Ask too whether PHP was restarted after the update: installing the fix doesn't protect PHP processes that were already running.
Yes. On October 26, 2026, the US Cybersecurity and Infrastructure Security Agency (CISA) added both flaws to its Known Exploited Vulnerabilities catalog. Amazon Threat Intelligence logged attempts against its honeypots from October 17, four days before public disclosure, and says PHP2Shell is now seeing broad exploitation attempts in the wild. On October 24 a researcher reported successfully exploiting three honeypot servers running unpatched PHP 8.4, and on October 26 Trail of Bits confirmed working exploits against unpatched PHP 8.2 to 8.5. As of October 28, Tenable knew of one reported compromise, against firewall appliances rather than websites, which it had not confirmed. Amazon advises starting any investigation from October 17, not the disclosure date.

The next analysis lands Sunday. Get the Briefing →

Who patches the layer under your site?

Get an honest read on your WordPress setup

We'll look at what your site runs on, who is responsible for each layer, and what it would take to keep it current. If staying on WordPress is the better call, we'll say so.