# PHP2Shell (CVE-2026-109618 and CVE-2026-109619): What Website Owners Should Do Now

> PHP2Shell is a pair of critical PHP flaws patched Oct 21, 2026 and now hit by millions of exploit attempts. Who's affected and how to protect your site.

- URL: https://www.netembark.com/2026/10/23/php2shell-php-vulnerability-what-to-do/
- Published: 2026-10-23
- Updated: 2026-10-23
- Author: Gary Pyatigorsky

---

**Quick answer:** PHP2Shell is two critical PHP flaws, CVE-2026-109618 and CVE-2026-109619, both rated CVSS 9.2. They affect PHP 5.4 through 8.5.11 and can allow remote code execution. Patches came out October 21, 2026. If your site runs PHP, ask your host to confirm you're on 8.5.12, 8.4.27, 8.3.36 or 8.2.35.

## What happened

On October 20, 2026, the PHP project announced an upcoming security release for two critical vulnerabilities ([Sophos](https://www.sophos.com/en-us/blog/proof-of-concept-exploit-released-for-php-vulnerabilities-109618-109619)). Details leaked online that same day, and proof-of-concept exploit code started spreading ([SecurityWeek](https://www.securityweek.com/php2shell-exploitation-started-days-before-patches/)). The fixes were released on October 21, after the PHP Foundation and industry partners spent weeks building and validating them (SecurityWeek).

Google Cloud describes the two flaws this way ([Google Cloud](https://cloud.google.com/blog/products/identity-security/responding-to-core-php-vulnerabilities-cve-2026-109618-cve-2026-109619)):

- **CVE-2026-109618:** out-of-memory handling can interrupt PHP while internal request data is only partly set up. Cleanup may then treat that invalid data as valid.
- **CVE-2026-109619:** internal state tied to one request can survive after its memory has been freed. A later request on the same worker may then use that stale state.

Amazon Threat Intelligence logged an exploit attempt against its honeypots on October 17, four days before public disclosure, coming from a commercial anonymization network ([AWS Security Blog](https://aws.amazon.com/blogs/security/amazon-threat-intelligence-identifies-php2shell-exploitation-prior-to-public-disclosure-in-madpot/)). Cloudflare CEO Matthew Prince said attempts across Cloudflare's network grew from thousands before the announcement to "millions now" by early October 22 (SecurityWeek). The Guardian reported that the US National Security Agency warned the flaw could let attackers take control of web servers and steal data, and that some government websites were briefly taken offline to install the patch ([The Guardian](https://www.theguardian.com/technology/2026/oct/22/websites-across-world-hit-by-millions-of-attempts-to-exploit-php-code-flaw)).

According to CBS News, Wall Street Journal reporter Robert McMillan, who first reported the issue, said researchers found the flaws using an OpenAI AI model, and that the bug had existed for at least a decade. SentinelOne's Andrés Guerrero-Saade told CBS that the case shows how AI is speeding up both vulnerability research and attackers, which shrinks the gap between a patch being released and attacks against it. CBS also reported that the FBI's cyber division posted on X advising organizations that can't patch right away to take their sites offline temporarily ([CBS News](https://www.cbsnews.com/news/php2shell-vulnerability-ai-security-flaw/)).

**Some context.** The volume of attempts is huge, but so far the evidence of actual break-ins is limited. watchTowr said the exploits it saw being sprayed around "either don't work at all, test for timing-based differences, or crash the target" (SecurityWeek). Sophos withdrew an earlier report of a successful compromise and said that, as of October 22, it had found no evidence of one (Sophos). That gives site owners a window to patch. It doesn't mean they can wait.

![Timeline titled "PHP2Shell, October 17 to 22, 2026." October 17: Amazon logs an exploit attempt on its honeypots before disclosure. October 20: PHP announces an upcoming security release and details leak online. October 21: PHP releases fixes in 8.5.12, 8.4.27, 8.3.36 and 8.2.35. October 22: Cloudflare reports millions of exploit attempts, while Sophos reports no evidence of a successful compromise. Sources: AWS, Sophos, SecurityWeek, php.net. Netembark logo and netembark.com.](https://www.netembark.com/wp-content/uploads/2026/10/php2shell-timeline.png)

## Who is affected

According to Google Cloud, every PHP version from 5.4 through 8.5.11 is vulnerable. Sophos reports that PHP itself said "all PHP installations serving web requests" are at risk. That includes most WordPress, Drupal, Joomla, Magento and custom PHP sites. The Guardian notes that PHP underpins about 70% of websites.

The highest-risk group is sites still running **PHP 8.1 or older**. Those versions are end-of-life, and the PHP project isn't releasing fixes for them (Google Cloud). The only options there are an upgrade or a backported patch from your host or Linux vendor.

## How to check your site

1. **Find your PHP version.** You can usually see it in your hosting control panel (cPanel, Plesk or your host's dashboard). WordPress users can also go to *Tools › Site Health › Info › Server*.
2. **Compare it to the patched releases:** 8.5.12, 8.4.27, 8.3.36 or 8.2.35 or newer (Google Cloud).
3. **Ask your host in writing** whether the server has been patched or has a vendor backport. This matters most on shared hosting, where you may not control PHP yourself.
4. **Look for warning signs.** Watch for unexpected crashes or 500 errors, unfamiliar files or admin users, and outbound traffic you can't explain. Sophos has published indicators tied to a Mirai-variant botnet payload seen in blocked attempts (Sophos).

PHP2Shell explained: a 60-second video from Netembark.

### Video transcript

1. This week, a serious pair of PHP flaws called PHP2Shell made headlines. They're tracked as CVE-2026-109618 and CVE-2026-109619, each rated CVSS 9.2.
2. Every PHP version from 5.4 through 8.5.11 is affected. PHP runs a large share of the web, including WordPress.
3. Patches came out October 21. Exploit attempts are in the millions, though researchers say the attempts they've seen haven't succeeded so far.
4. Check your PHP version and update to 8.5.12, 8.4.27, 8.3.36 or 8.2.35. On PHP 8.1 or older? Plan an upgrade, because no official fix is coming.
5. Netembark builds custom HTML, WordPress and AI-built sites. HTML and AI-built sites, forms included, don't run PHP, so they aren't exposed to this flaw. For WordPress, we keep hosting, PHP versions and domain details up to date, and we can move older sites to a non-PHP build.
6. Not sure your site is patched? Book a call at netembark.com/contact-us, call 800-707-2697, or email info@netembark.com.

## How to protect your site

- **Patch first.** Updating PHP is the actual fix. PHP's own advisory says there are no complete mitigations ([php.net](https://www.php.net/archive/2026.php#2026-10-21-5)). A firewall rule only reduces the risk while you get there.
- **Upgrade off end-of-life PHP.** If you're on 8.1 or older, plan the move to a supported version now and test plugins and themes on a staging copy first.
- **Turn on web application firewall protection** from your host, CDN or security plugin as a temporary layer. Several providers, including Cloudflare and Patchstack, reported seeing the attack traffic (SecurityWeek).
- **Make sure you have a recent, off-server backup** before making changes.
- **Keep your access details current.** If you don't know who controls your hosting login, your domain registrar or your DNS, you can't patch quickly. In incidents like this one, that is often what slows people down.

## How Netembark helps

Netembark builds three kinds of websites: custom HTML sites, WordPress sites and AI-built sites. Here is how PHP2Shell relates to each.

**1. Custom HTML and AI-built sites.** These sites, including their forms, don't run PHP. That means they aren't exposed to the PHP2Shell flaw or to PHP request-handling flaws like it. To be clear, no site is unhackable. These sites still need secure hosting, protected logins and up-to-date components. This particular PHP vulnerability just doesn't apply to them.

**2. WordPress sites.** WordPress runs on PHP, so these sites need the patch. For our clients, Netembark keeps the hosting, the PHP version and the domain information up to date, so when an advisory like PHP2Shell comes out, we know which sites need attention and who to contact. For older WordPress sites, especially those stuck on PHP 8.1 or earlier, we can also move the site onto a non-PHP build.

**Not sure whether your site is patched?** [Contact us](https://www.netembark.com/contact-us/), email [info@netembark.com](mailto:info@netembark.com), or call [(800) 707-2697](tel:+18007072697). We'll help you find out what your site runs and what to do next.

## FAQ

**What is PHP2Shell?**
 PHP2Shell is the name for two critical PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619, both rated CVSS 9.2. They can allow remote code execution on servers running PHP 5.4 through 8.5.11.

**Which PHP versions fix PHP2Shell?**
 PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP 8.1 and older won't receive official fixes.

**Is my WordPress site affected?**
 If its server runs an unpatched PHP version, yes. WordPress runs on PHP. Check your PHP version and confirm with your host.

**Have sites actually been hacked?**
 Attempts number in the millions. As of October 22, 2026, Sophos and watchTowr said the attempts they observed hadn't succeeded, but patching is still urgent.

**Is a static or non-PHP website immune to hacking?**
 No. It isn't exposed to this PHP flaw, but it still needs good security practices.

## Sources

1. SecurityWeek, "PHP2Shell Exploitation Started Days Before Patches," Oct 22, 2026. https://www.securityweek.com/php2shell-exploitation-started-days-before-patches/
2. The Guardian, "Websites across world hit by millions of attempts to exploit PHP code flaw," Oct 22, 2026. https://www.theguardian.com/technology/2026/oct/22/websites-across-world-hit-by-millions-of-attempts-to-exploit-php-code-flaw
3. AWS Security Blog, "Amazon Threat Intelligence identifies PHP2Shell exploitation prior to public disclosure in MadPot." https://aws.amazon.com/blogs/security/amazon-threat-intelligence-identifies-php2shell-exploitation-prior-to-public-disclosure-in-madpot/
4. Sophos CTU, "Proof-of-concept exploit released for PHP vulnerabilities (CVE-2026-109618, CVE-2026-109619)," updated Oct 22, 2026. https://www.sophos.com/en-us/blog/proof-of-concept-exploit-released-for-php-vulnerabilities-109618-109619
5. Google Cloud, "Responding to core PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619." https://cloud.google.com/blog/products/identity-security/responding-to-core-php-vulnerabilities-cve-2026-109618-cve-2026-109619
6. PHP Group (php.net), "Critical remote code execution vulnerabilities, update now," security advisory, Oct 21, 2026. https://www.php.net/archive/2026.php#2026-10-21-5
7. CBS News, "What to know about the PHP bug affecting 70% of the world's websites," updated Oct 22, 2026. https://www.cbsnews.com/news/php2shell-vulnerability-ai-security-flaw/

Netembark LLC · Google Premier Partner (2023) · Freehold, NJ · (800) 707-2697 · info@netembark.com

---

Site index for agents: https://www.netembark.com/llms.txt
