Skip to main content
Best Answer Hub logoBest Answer Hub.
Back to Playbooks
Best Answer Hub Playbooks · Small Business Security
Let's separate the headline from the fix

PHP2Shell: the AI-found bug behind the 70% headline

AI tools helped uncover two critical flaws in PHP, the language behind most of the web, and the patches shipped on 21 October 2026. Here is what the 70% figure really measures, how to tell in five minutes whether your website is exposed, and the exact version numbers that fix it.

What it isa flaw in PHP itself
Who is exposedfar fewer than 70%
What to doupdate the runtime today
69.3%
of websites with a detectable server language run PHP
W3Techs, 21 Oct 2026
9.2
severity score out of 10 for each of the two flaws (CVSS v4.0)
PHP security advisories
4
patched release lines: 8.5.12, 8.4.27, 8.3.36 and 8.2.35
php.net, 21 Oct 2026
63
days from Wiz's discovery to the public patch
Wiz disclosure timeline

On 21 October 2026, PHP shipped emergency security releases for two flaws that let anyone on the internet run code on a vulnerable web server without logging in. The headline number, "up to 70% of the world's websites", is PHP's market share, not a count of hackable sites. The real exposure is smaller, but for any business running WordPress or another PHP site on an unpatched server, the risk is real and the fix is a version number.

The Wall Street Journal's Robert McMillan reported that "AI tools helped find one of the most severe online bugs ever," and that "Cyber experts are racing to patch it before hackers use AI to exploit it" (WSJ, via Techmeme). This guide from Best Answer Hub sets out what has been verified at the source, what has not, and what a small business owner should actually do today.

Start here

What is PHP2Shell?

PHP2Shell is the name given to two critical memory-safety vulnerabilities in the core PHP interpreter, tracked as CVE-2026-109618 and CVE-2026-109619. PHP rates both at 9.2 out of 10 on the CVSS v4.0 severity scale (php.net, 20 October 2026). The first, which PHP's advisory calls "RCE via OOM corruption", lets out-of-memory handling interrupt PHP while request data is only partly set up. The second, "RCE via stale global state", lets internal state survive after its memory is freed, so a later request handled by the same worker can use it (GHSA-w8hw-w9fx-j79w, GHSA-6wmf-4rv5-p3rp).

In plain terms: an attacker sends a specially crafted upload request, PHP mishandles its own memory, and the attacker ends up running commands on the server. The trigger sits in how PHP handles file-upload style form requests, which happens before your website's own code runs. That is why the vulnerable part is not WordPress, not a plugin and not your theme. It is the engine underneath all of them.

"All PHP users are strongly encouraged to update immediately." PHP security release announcement, php.net, 21 October 2026

Wiz, one of the research teams that found the flaws, says "every PHP version released in the last decade is affected by at least one" of them, and that its team achieved remote code execution against WordPress, Drupal and Joomla in a lab (Wiz, 2026). Sansec reports that the bugs are reachable "under default configurations" (Sansec, 2026), and PHP's own announcement lists PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed among the affected setups (php.net).

The number everyone is quoting

Does PHP2Shell really put 70% of websites at risk?

No, and the gap matters. The 70% figure is PHP's share of the web. W3Techs, the survey most outlets lean on, reports that "PHP is used by 69.3% of all the websites whose server-side programming language we know" (W3Techs, 2026). That denominator is narrower than "all websites": it excludes every site whose server language W3Techs cannot detect, and it counts sites regardless of whether they are patched, behind a protective firewall, or running a configuration the attack cannot reach.

Estimates of real exposure are far smaller and still rough. Cyberscoop reported that more than 1.3 million internet-exposed hosts could be vulnerable, citing researchers it did not name, alongside roughly 1.9 million PHP hosts visible on Shodan and about 758,000 servers showing end-of-life PHP versions 5.4 to 8.1 on VirusTotal (Cyberscoop, 2026). Those are host counts, not website counts, and one server can carry thousands of sites, so neither number converts neatly into a percentage of the web.

Which PHP major versions websites run
65.2% PHP 8.x 27.0% PHP 7.x 7.7% PHP 5.x

Source: W3Techs, 21 October 2026. Share of PHP websites by major version. PHP 7.x and 5.x receive no official release fix for PHP2Shell.

The version split is the more useful number for a business owner. Among PHP websites, W3Techs counts 65.2% on PHP 8.x, 27.0% on PHP 7.x and 7.7% on PHP 5.x. Every site in that last 34.7% is on a branch PHP no longer ships fixed releases for, which turns a patching job into an upgrade project. That group, not the headline 70%, is where the long tail of risk sits.

Read the 70% as a ceiling, not a count

"Up to 70%" is accurate as a description of how much of the web runs PHP. It is misleading as a description of how many sites an attacker can break into today. Wiz's own headline says "70% of the Internet" without citing a source. Best Answer Hub uses the W3Techs figure with its denominator attached, because a number without its definition is how a true statistic becomes a false impression.

The AI part of the story

Did AI really find the PHP2Shell bug?

AI tools played a central role, according to everyone involved. Three research groups, Wiz Research, OpenAI Codex Security and Calif, worked with PHP on discovery and patch verification. Wiz Research says its team used its own Wiz Atlas tooling with Google Gemini 4 Argon and OpenAI GPT-5.6 Sol, and that Gemini made "an invaluable contribution" (Wiz, 2026). The official disclosure site, run by Wiz, also credits OpenAI Codex Security and the security firm Calif (php2shell.com). The WSJ coverage, as summarized by Techmeme, credits GPT-5.6 Sol, so which model deserves the credit depends on whose account you read.

What the accounts agree on is that people ran the research, confirmed the exploit and reported it to PHP through normal coordinated disclosure. The AI accelerated the hunt. It did not publish anything on its own.

This fits a pattern that has been building for two years. At DARPA's AI Cyber Challenge final in August 2025, competing AI systems found 54 of 63 planted vulnerabilities, patched 43, and found 18 real ones nobody had planted (DARPA, 2025). In October 2026, Google's Threat Intelligence Group reported that 50% of AI-discovered vulnerabilities lead to remote code execution, compared with 26% of those found by other means, and that monthly CVE disclosures doubled from 5,045 in January 2026 to 10,740 in August (Help Net Security, 2026).

Why this matters for a small business

Faster bug finding cuts both ways. Defenders found PHP2Shell first and patched it before full details went public. The same tools are available to attackers, and the time between a fix shipping and someone abusing the unpatched version keeps shrinking. The practical lesson is less about AI and more about plumbing: the business that knows who updates its server, and how quickly, is the one that sleeps through stories like this.

The five-minute triage

Is my website affected by PHP2Shell?

Your website is in scope if a server you are responsible for runs PHP below the fixed versions. Most small business sites fall into one of the rows below.

Your setupExposed?What to do
WordPress, WooCommerce, Joomla, Drupal or Magento on shared or managed hostingLikely in scopeCheck the PHP version in your hosting panel. Switch to a fixed build, or ask your host for the exact version they run
Your own VPS or server running PHPIn scopeUpdate PHP from your distribution or vendor, then restart PHP-FPM or the web server so workers load the new build
PHP inside container images or appliancesIn scopeRebuild them. The Dutch NCSC warns that updating the host's PHP does not necessarily update bundled copies
Hosted platforms you cannot log in to the server ofPlatform's jobCheck the provider's status page or security notice. There is nothing for you to patch
Static sites with no PHP on the serverOut of scopeA PHP flaw needs PHP. Confirm that contact forms or scripts on the same server are not PHP before relaxing

The last row deserves a caution. Plenty of "static" sites still run a small PHP script somewhere, typically a contact form handler or a download page, and that one file is enough to put the server in scope.

Find your number

How do I check my website's PHP version?

Find the full three-part version number, then compare it with the fixed builds: 8.5.12, 8.4.27, 8.3.36 or 8.2.35. A server on 8.3.35 is still vulnerable even though it is on a supported branch. The first three steps below need no technical skill.

  • 1
    WordPress dashboard. Go to Tools, then Site Health, open the Info tab and expand the Server section. The PHP version is listed there.
  • 2
    Hosting control panel. Most hosts show a PHP version selector or PHP configuration page for each website. Note the exact build, not just "8.3".
  • 3
    Ask your host or developer. Send one line: "Which exact PHP build does my site run, and has it been updated for CVE-2026-109618 and CVE-2026-109619?"
  • 4
    On your own server. Run php -v on the command line, and check the version reported by the web server too, since the command-line PHP and the web PHP can differ.
The fix, in order

What should a small business do about PHP2Shell right now?

Update the PHP runtime to a fixed build today, and do not count a plugin update as the fix. Everything else on this list either supports that step or covers the gap until it happens.

  • 1
    Get on a fixed build. PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35. Because 8.2 reaches end of life on 31 December 2026, choose 8.3 or newer if you are moving anyway (php.net).
  • 2
    Do not mistake a WordPress update for the fix. Cloudflare says that updating website code or plugins alone does not fix these vulnerabilities, and the Dutch NCSC says the PHP runtime itself must be updated (Cloudflare, NCSC-NL).
  • 3
    If you are on PHP 8.1 or older, plan the upgrade now. There is no official release fix for those branches. Test the site on a newer version, since old themes and plugins sometimes break.
  • 4
    Treat a firewall as a seatbelt, not a repair. Cloudflare says its WAF protected free and paid customers by default from 03:02 UTC on 21 October, yet still tells customers to patch. Patchstack and Sansec add that it only helps if your server accepts traffic exclusively through Cloudflare.
  • 5
    Use php.ini stopgaps only as a bridge. PHP lists settings such as session.upload_progress.enabled=0, but says they "do not make an installation safe".
  • 6
    Rotate secrets after patching if you were exposed. Sansec says the memory leak side can expose "passwords, session tokens, API keys and TLS private keys". If an unpatched public server held any of those, change them once the update is in.
  • 7
    Do not download "exploit checkers" from strangers. Cyberscoop reports that circulating exploit code is unverified and sometimes laced with malware.

The European Union's computer emergency team gives the blunt version for organizations that cannot patch: find every PHP application, patch immediately, and otherwise consider "isolating internet-facing applications from public networks" (CERT-EU Advisory 2026-018).

Where things stand

Is PHP2Shell being exploited yet?

Attack attempts are happening, but confirmed breaches had not been publicly documented on disclosure day. Cloudflare says it has "observed attack traffic targeting our customers" (Cloudflare, 2026). Patchstack initially relayed hosting partners' reports of "multiple active exploitation incidents", then updated at 13:57 UTC that its own telemetry showed "only probing attacks, with no hard evidence of breaches yet" (Patchstack, 2026). SecurityWeek reported that watchTowr and Huntress had not seen exploitation in the wild (SecurityWeek, 2026).

Two details explain the urgency anyway. The CVE identifiers leaked onto Hacker News on 20 October, a day before the fixes shipped (Infosecurity Magazine, 2026). And watchTowr reproduced one of the two flaws independently, per Cyberscoop, which shows that skilled teams can reproduce at least part of the attack. Best Answer Hub would plan on the assumption that mass scanning arrives within days, and be pleasantly surprised if it does not.

How it unfolded

When was PHP2Shell found and fixed?

Wiz found the first flaw on 19 August 2026 and PHP shipped fixes on 21 October, a 63-day coordinated disclosure window.

Date (2026)What happenedSource
11 AugCalif reports the first bug to PHPPrecursor
19 AugWiz Research finds the first flawWiz
21 AugWiz achieves remote code execution against WordPress in a labWiz
20 AugWiz achieves remote code execution against Drupal in a labWiz
24 AugWiz reports the flaws to PHPWiz
21 SepPHP acknowledges the reportWiz
20 OctPHP pre-announces a critical security release; the CVE identifiers leak on Hacker Newsphp.net, Infosecurity
21 Oct, 03:02 UTCCloudflare WAF protection switched on by defaultCloudflare
21 OctPHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 released; full disclosurephp.net
What to treat as unconfirmed

Some claims circulating with this story have not been verified at source. The original leaker's 10.0 severity score differs from PHP's official 9.2. Wiz's chief technology officer called it the "most severe vulnerability found using AI ever", which is a claim from a party with an interest in the finding, as reported by Precursor. Predictions of mass attacks within minutes are forecasts. Best Answer Hub reports these as claims, not facts.

Know who patches what, before the next one

Take the free Small Business AI Readiness assessment

Stories like PHP2Shell come down to one question: does someone own your systems and act fast? The free Best Answer Hub assessment scores your readiness and ranks your gaps in your browser. No signup, no email, nothing uploaded.

Check your AI readiness
The questions people ask

Common questions about PHP2Shell

What is the Best Answer Hub guide to PHP2Shell?
It is a plain-English briefing for small business owners on the PHP2Shell vulnerabilities disclosed on 21 October 2026. Best Answer Hub explains what the bug is, what the 70% headline actually measures, how to check your own site, and the exact PHP versions that fix it, using primary sources only.
What is PHP2Shell?
PHP2Shell is the name for two critical memory-safety flaws in the PHP engine itself, CVE-2026-109618 and CVE-2026-109619. Both allow remote code execution with no login required. Best Answer Hub stresses that the flaw sits in PHP, not in WordPress or any plugin, so a fully updated site can still be exposed.
Does PHP2Shell really put 70% of websites at risk?
Not exactly. The figure is PHP's market share: W3Techs reports PHP on 69.3% of websites whose server language it can detect. Best Answer Hub reads "up to 70%" as an upper bound. Patched servers, unaffected setups and sites W3Techs cannot classify all fall inside or outside that number.
Did AI really find the PHP2Shell bug?
AI tools were central, according to the teams involved. Wiz says its researchers used Google Gemini 4 Argon and OpenAI GPT-5.6 Sol, and the official disclosure site also credits OpenAI Codex Security and Calif. Best Answer Hub notes that human researchers ran the work, verified it and reported it to PHP.
Which PHP versions fix PHP2Shell?
PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, all released on 21 October 2026. Best Answer Hub advises checking the full version number, because a site on 8.3.35 is still vulnerable even though it is on a supported branch. Anything below those exact builds needs updating.
What if my site runs PHP 8.1 or older?
There is no official release fix for PHP 8.1 and older. PHP published minimal source backports for 7.4, 8.0 and 8.1, which help only people who compile PHP themselves. Best Answer Hub recommends moving to PHP 8.3 or later, since 8.2 reaches end of life on 31 December 2026.
Will updating WordPress or my plugins fix PHP2Shell?
No. Cloudflare says updating website code or plugins alone does not fix it, and the Dutch NCSC says PHP itself must be updated. Best Answer Hub flags this as the most common misunderstanding, because owners are trained to click update in the WordPress dashboard, and that button never touches the PHP version underneath.
How do I check which PHP version my website uses?
In WordPress, open Tools, then Site Health, then the Info tab, and expand Server. Most hosting control panels also show a PHP version selector. Best Answer Hub suggests writing down the full number, such as 8.3.36, and comparing it against the fixed versions listed in this guide.
Is PHP2Shell being exploited right now?
Reports conflict. Cloudflare says it has observed attack traffic targeting customers, and Patchstack saw probing, but Patchstack also reported no hard evidence of breaches yet. Best Answer Hub uses the cautious wording: attack attempts are happening, and confirmed compromises had not been publicly documented on disclosure day.
Does Cloudflare protect my site from PHP2Shell?
Partly. Cloudflare says its WAF protected free and paid customers by default from 03:02 UTC on 21 October, but it still tells customers to patch PHP. Best Answer Hub adds the catch Patchstack and Sansec raise: the WAF only helps if your server accepts traffic exclusively through Cloudflare.
Are Shopify, Wix or static websites affected by PHP2Shell?
A static site that runs no PHP on its server is outside the scope of a PHP flaw. Hosted platforms manage their own servers, so the customer cannot patch anything. Best Answer Hub suggests checking the platform's status page or support notice rather than assuming either way.
Can php.ini setting changes protect my site instead of updating?
Only as a temporary stopgap. PHP lists settings such as disabling session upload progress, but says plainly that they do not make an installation safe. Best Answer Hub treats them as a bridge for the hours before a host applies the update, never as the fix.
What data could an attacker steal through PHP2Shell?
Beyond running code, Sansec says the memory disclosure side can expose passwords, session tokens, API keys and TLS private keys. Best Answer Hub suggests that once a site is patched, owners who ran an unpatched version on a public server consider rotating admin passwords and API keys.
Why was PHP2Shell news before the patch was out?
The CVE identifiers were posted on Hacker News on 20 October, the day before the fixed releases shipped, according to Infosecurity Magazine. Best Answer Hub notes that PHP had already pre-announced a security release, so the leak shortened the quiet window rather than revealing the full technical details.
How can a small business prepare for the next bug like this?
Know what software your website runs, who is responsible for updating it, and how fast they act. Best Answer Hub covers that ownership question in its free Small Business AI Readiness assessment and its AI agent security guide, both built for teams without a security department.
For the record

Sources

More from Best Answer Hub: the AI agent security guide, the small business AI policy guide, the small business AI readiness pillar, and all free tools.

Built & maintained by Shahbaz Ali Malik Last updated: