PHP2Shell (CVE-2026-109618 and CVE-2026-109619): The Dual RCE Running Below WordPress That No Plugin Update Can Fix

digital interactive web development hero image

The Floor of the Building Has a Hole

Your WordPress plugin audit is not going to catch this one.

Two critical remote code execution vulnerabilities in PHP itself went public on October 21, 2026. They are tracked as CVE-2026-109618 and CVE-2026-109619 and carry a CVSS v4.0 score of 9.2 apiece. Researchers started calling them PHP2Shell immediately, and the name is accurate: an attacker sends a crafted HTTP request and, on an unpatched server, gets a shell. No WordPress account required. No plugin involved. No application-layer defense stops it.

This is not a WordPress vulnerability. It is a flaw in the PHP runtime that WordPress runs on top of. Every update you pushed to client plugins this week did not touch it.

How the Two Flaws Work

CVE-2026-109618 lives in PHP’s memory management during request setup. When PHP runs out of memory partway through parsing a multipart form submission, it exits via a long jump. The problem is that request data may only be half-initialized at that point. Cleanup code then treats that half-built state as valid, and an attacker who can push PHP into that out-of-memory condition can redirect execution from there. Multipart form parsing, the format browsers use for any file upload, is one confirmed path to trigger it.

CVE-2026-109619 is a stale global state problem. PHP workers in persistent execution environments retain internal state that outlives the memory behind it. A later request on the same worker can act on that leftover data before normal initialization resets it. Session upload progress handling is one confirmed trigger path. On PHP 8.5, fatal error backtrace generation is another. The flaw is especially relevant to PHP-FPM, the process model used by virtually every performance-optimized WordPress hosting stack on the market today.

Apache mod_php is also affected. PHP’s own advisory rated it the highest-risk execution environment for these two flaws.

Beyond code execution, CVE-2026-109618 carries a memory disclosure component. PHP’s upload-progress handler can return freed worker memory to the client inside a PHPSESSID response cookie. That memory can contain passwords, session tokens, API keys, and TLS private keys from entirely different requests on the same server. The handler runs before any application code, which means the leak path works even when the WordPress application never calls session_start().

The vulnerable code path for CVE-2026-109618 traces back to PHP 5.4.0, released in 2012.

What the Exploitation Timeline Actually Looks Like

Amazon Threat Intelligence observed exploitation attempts against their MadPot honeypot network on October 17, four days before public disclosure, suggesting the vulnerability was either leaked or independently discovered before the coordinated release date.

The PHP security team accelerated their release timeline after details appeared on Hacker News on October 20. Patches shipped on October 21 at approximately 13:00 UTC. By 08:44 UTC that same morning, one managed WordPress host was already seeing requests targeting their platform using a public proof-of-concept.

October 24: researcher Adel Karimi confirmed successful exploitation against three honeypot servers running PHP 8.4.26. Shells executed attacker commands. October 26: Trail of Bits confirmed working exploits against pre-patch releases of PHP 8.2 through 8.5 and demonstrated a shell on MediaWiki, Symfony, Laravel, and phpBB.

Palo Alto Networks’ Cortex Xpanse telemetry flagged over 22.6 million potentially exposed PHP instances as of October 25. This is active exploitation at scale.

Where WordPress Sites Actually Stand

WordPress runs on PHP. Every page request your server handles starts by spinning up PHP, which then loads WordPress core, your theme, and every active plugin. The vulnerability is not in that code. It is in the runtime that executes it.

No WordPress plugin protects against PHP2Shell. No security plugin, no WAF running inside WordPress, and no WordPress core update addresses the underlying PHP engine flaw. Frameworks and CMSs built on PHP including WordPress, Drupal, Laravel, and Magento are all affected when they run on a vulnerable PHP runtime.

Fixed PHP versions are 8.5.12, 8.4.27, 8.3.36, and 8.2.35. For end-of-life branches (PHP 8.1, 8.0, and 7.4), the PHP security team released minimal source backports specifically because of the severity, but those branches will not receive further security patches. PHP 8.2 itself reaches end of life on December 31, 2026.

The fastest check for any WordPress site: go to Tools > Site Health, open the Info tab, expand Server, and read the PHP version field. If it is below the fixed versions listed above, the runtime is still vulnerable regardless of how current your plugins are.

One caveat: a regression in PHP 8.4.27 and 8.5.12 can crash processes in applications using the SimpleXML extension. PHP traced it to a separate garbage collector fix bundled into those releases, unrelated to the PHP2Shell patches themselves. A fix was merged into the PHP source but had not shipped in a release as of October 26. If client sites rely on SimpleXML, test the upgraded runtime on staging before pushing to production.

Also unresolved: CVE-2026-115560, a third session upload progress flaw PHP disclosed on October 23. It is a different code path from the PHP2Shell pair and is not fixed in the October 21 releases. The current guidance from PHP is to set session.upload_progress.enabled=0 in php.ini until the next routine bugfix release ships.

What Managed Hosts Have Done

WordPress.com, Pressable, WP Cloud, and Tumblr, all Automattic properties, patched platform-wide and require no action from site owners. Some managed WordPress hosts applied the patch in an emergency maintenance window on October 21. Vercel deployed WAF rules before public disclosure. Those WAF rules reduce exposure to known exploit patterns but do not replace patching the runtime itself.

Self-hosted environments on VPS or dedicated servers where the site owner or agency controls the PHP runtime need immediate manual action. This applies to any cPanel-based shared hosting account where PHP version management is exposed to the account holder. It also applies to every client site your agency manages on a server you control.

What to Do Now

Check the PHP version in Tools > Site Health on every site you manage. Update via your hosting control panel to the patched release for your branch. Move PHP 8.1 sites to 8.3 or 8.4 rather than 8.2, which expires December 31, 2026. Apply session.upload_progress.enabled=0 in php.ini as an interim mitigation for CVE-2026-115560 until PHP ships that separate fix. Audit server logs back to at least October 17, the earliest confirmed exploitation date, for unusual POST requests to multipart upload endpoints.

If your agency manages client servers directly, start with the PHP version inventory before touching anything else.

Frequently Asked Questions

My host says they have patched. Why should I still check Tools > Site Health?

Some hosts deploy server-side fixes that do not immediately update the version string visible inside WordPress. The version shown in Tools > Site Health is the PHP version your site is actually running. If that number is below 8.2.35, 8.3.36, 8.4.27, or 8.5.12, ask your host to confirm their deployment reached your specific account or server.

Does disabling session.upload_progress.enabled fully protect against both CVEs?

No. It blocks one confirmed trigger path. CVE-2026-109618 has other paths to the out-of-memory state. CVE-2026-109619 has additional trigger paths beyond session upload progress, including fatal error backtraces on PHP 8.5. The setting is an interim measure while you arrange the PHP runtime upgrade.

We run Nginx plus PHP-FPM. Is that higher or lower risk than Apache mod_php?

PHP rated mod_php the highest-risk environment and confirmed a working exploit there. PHP-FPM is also affected. CVE-2026-109619’s stale global state mechanism is inherent to persistent worker processes, which PHP-FPM uses. Both execution models need the PHP runtime updated.

Client sites are on PHP 8.1. Can they stay there with the source backport?

PHP released minimal source backports for 8.1, 8.0, and 7.4 due to severity. Most shared hosts will not deploy a source backport. If your client’s host has not explicitly confirmed they applied it, assume the 8.1 installation is still exposed. Migrate to PHP 8.3 or 8.4. Moving to 8.2 buys only two months before another forced upgrade on December 31.

Is CISA tracking these CVEs?

As of October 23, neither CVE-2026-109618 nor CVE-2026-109619 had been added to CISA’s Known Exploited Vulnerabilities catalog. That status does not change the exploitation evidence. Amazon Threat Intelligence confirmed attempts starting October 17. Trail of Bits confirmed working exploits on October 26. Treat these as actively exploited.


Sources: