On the morning of October 21, 2026, a strange thing happened across the internet. Websites started switching themselves off.
The Dutch National Cyber Security Centre went dark. So did French prefecture sites, several German federal sites, the Port of Rotterdam and a number of Dutch hospitals. That afternoon, the Czech government took its website offline. Wikimedia pulled some of its systems as a precaution. UptimeRobot, which monitors sites around the world, saw downtime alerts spike to about 37,000 a minute at peak, roughly 11 times the previous day’s level. Among the sites it watches, unreachable Dutch (.nl) domains more than tripled overnight.
Most of these sites had not been hacked. They went offline on purpose, because a critical flaw in PHP, the language behind WordPress, Drupal, Magento and Laravel, was already under attack, and their owners had no other safe option yet.
That’s the part worth sitting with. For many organizations, “turn the website off” was the plan.
What happened with PHP2Shell
The flaws, nicknamed PHP2Shell (CVE-2026-109618 and CVE-2026-109619), let an attacker run code on a server without logging in. Both are rated 9.2 out of 10. CISA, the U.S. Cybersecurity and Infrastructure Security Agency, said they affect every PHP installation serving web requests. Its advice to anyone who couldn’t patch right away was blunt: take PHP-based systems offline until they can be updated.
Normally, a flaw like this stays secret until the fix is ready. Then the patch and the announcement go out together, so attackers get no head start. This time, that process broke down:
- October 17: Amazon’s honeypots caught the first exploitation attempt, four days before any patch was public.
- October 20: The CVE numbers leaked on online forums. PHP moved its release up a day.
- October 21, early morning: A software distributor published patched builds more than six hours ahead of schedule, giving attackers a fix to study. A researcher accidentally posted, then deleted, a video of the exploit working.
- October 21, 14:00 UTC: The official patch shipped. Cloudflare had already seen thousands of attack attempts in the 10 hours before. Within two hours of the release, that grew to hundreds of thousands, and later to millions.
By the end of release day, Censys counted about 1.57 million internet-facing PHP hosts that still weren’t patched. On October 26, CISA added both flaws to its catalog of vulnerabilities known to be exploited in the wild.
The good news: officials in several countries reported attempts, not confirmed break-ins. The lesson: the organizations with the least disruption were the ones with a path other than switching off, such as someone ready to patch, test and deploy within hours.
AI has compressed the patch window
PHP2Shell wasn’t a one-off. It’s the most visible example of a trend that’s been building all year.
There are far more vulnerabilities to deal with
As of late October, 88,772 CVEs (public IDs for known vulnerabilities) had been published in 2026, more than all of 2023 and 2024 combined. IBM X-Force found that public CVEs across Microsoft, Oracle, Google Chrome and Apache rose from about 1,493 in January through September 2025 to more than 10,124 in the same months of 2026, a jump of roughly 578% that took off in April. That jump came as AI bug-hunting tools spread, and the bugs AI finds are serious ones: of 223 vulnerabilities it analyzed that were found with frontier AI models, 55% were rated High or Critical, and 91% could be reached over the internet.
Attackers move faster once a flaw is public
VulnCheck reports that the median time from a CVE being published to being confirmed as exploited fell from 120 days in 2025 to 80 days in the first half of 2026. Nearly a quarter of exploited flaws (23%) were attacked on or before the day they were disclosed. For WordPress, the numbers are starker. Patchstack found that for the most heavily exploited flaws, the median time to the first attack was five hours.
Attackers use AI too
IBM’s 2026 Cost of a Data Breach report found that more than one in four organizations hit by a malicious attack said AI was involved, up 56% from the year before. Those AI-driven breaches cost about $1 million more on average. In one documented case, a state-sponsored group used an AI coding agent to target about 30 organizations, with the AI doing an estimated 80 to 90% of the work.
It’s worth being precise here. AI isn’t writing every exploit that hits your site. VulnCheck found that only about 1.3% of AI-discovered vulnerabilities have been confirmed as exploited so far. What AI has done is flood the system with findings and make it cheaper to scan the whole internet for anything left unpatched. Once a fix is public, attackers can read it too, and automation does the rest.
It’s not just your CMS
Your website is a stack of software from dozens of sources. Every layer has needed critical fixes this year. And websites are squarely in the crosshairs: content management systems made up one-third of all actively exploited vulnerabilities VulnCheck tracked in the first half of 2026, mostly through WordPress plugins.
PHP and the CMS platforms built on it
PHP2Shell hit everything built on PHP at once. And the platforms on top of it had their own trouble:
- WordPress: 11,334 new vulnerabilities were found in the WordPress ecosystem in 2025, up 42% from 2024. 91% were in plugins, and 46% had no fix available when they were made public (Patchstack). Wordfence logged 497 in a single week in October 2026. WordPress core itself had flaws added to CISA’s exploited list this year.
- Drupal: A Highly critical SQL injection in Drupal core (CVE-2026-9082) is being actively exploited, and a Critical remote code execution fix for core followed in October.
- Adobe Commerce (Magento): A flaw rated 10.0 out of 10 (CVE-2026-75650) was attacked starting three days before Adobe released an emergency fix. Adobe also told merchants to rotate their encryption key and every credential. In a 2025 attack wave, Sansec saw 81% of Magento stores probed within weeks, while only 38% had patched.
Node.js and the npm supply chain
JavaScript sites carry a different kind of risk. On October 21, 2026, the same day as PHP2Shell, Node.js shipped fixes for 10 CVEs, including a High-severity flaw in its Brotli decoder that can lead to remote code execution. Versions past the end of life get no fix at all.
Then there’s the supply chain, the packages your developers install from npm. In September 2025, the Shai-Hulud worm poisoned more than 500 npm packages to steal GitHub tokens and cloud keys (CISA). On March 31, 2026, attackers hijacked a maintainer account for Axios, a library with more than 100 million weekly downloads, and published versions that installed a remote access trojan.
You don’t have to install a bad package on purpose. It arrives through an update, unless someone is checking.
Reacting costs far more than being ready
When a critical flaw lands, there are two ways it can go.
If you’re prepared: someone already watching the advisories flags it. A developer who knows your site applies the fix, tests it on staging and deploys it the same day. You get a short note saying what was patched and when.
If you’re not: the clock starts while you find someone who can help, get them access and explain how the site works. Meanwhile, you choose between leaving the site exposed and taking it offline. If an attacker gets in first, the cleanup takes days or weeks: removing malware, rebuilding from clean backups, rotating every password and key, and recovering from search-engine blocklisting.
The big averages make the point. IBM’s 2026 report puts the average breach at $4.99 million worldwide and $11.5 million in the U.S., and says breaches take 247 days on average to identify and contain. Those figures skew toward large enterprises. For most organizations, the real cost is more down to earth but still painful: emergency developer rates, days of lost orders or leads, damaged search rankings and customers who lose trust. Sites that take payments or store personal data can add breach notification and legal costs on top.
What “ready to go” maintenance looks like
The PHP2Shell timeline is a good checklist. At every step, the organizations that stayed online had something in place before the news broke.
Someone watching the advisories
Signs of PHP2Shell appeared days before the patch. A team that tracks vendor advisories, CISA’s exploited-vulnerability catalog and security feeds for your specific stack hears about trouble early, not from a customer.
Clear patch timelines
Agree in advance on how fast fixes get applied: same day for critical, actively exploited flaws, and on a set schedule for the rest. When the response is already approved, nobody waits on an estimate while the window closes.
A staging site and a test routine
A same-day patch is only safe if you can check it first. A staging environment and a repeatable test routine mean an emergency update doesn’t become an emergency outage.
Interim protection
Sometimes the patch isn’t out yet. Cloudflare had firewall rules running for PHP2Shell before the official fix shipped. A team that already manages your hosting and firewall can switch on protections like that right away.
A team that already knows your code
This is the one you can’t arrange on the day. A developer who knows your plugins, custom code, integrations and hosting can patch with confidence. One who’s seeing your site for the first time has to learn it under pressure.
Supported versions
Fixes only exist for supported software. PHP 8.1 and older got no PHP2Shell patch. PHP 8.2 reaches end of life on December 31, 2026, and Microsoft ends support for .NET 8 on November 10, 2026. Planned upgrades keep you on the side of the line where fixes arrive.
Be the site that stays online
The next PHP2Shell is coming. Nobody knows which platform or which week. What you can decide now is whether that day is a short, planned update or a scramble to find help while your site sits dark.
Atlantic BT’s support and maintenance team keeps WordPress, Drupal, Magento, Laravel, Umbraco and Node.js sites patched, monitored and tested, with developers who already know your codebase when it counts. Talk to us about keeping your site ready
Sources
- CISA, “Critical Vulnerabilities in PHP Require Immediate Patching” (Oct 21, 2026; KEV addition Oct 26, 2026): https://www.cisa.gov/news-events/alerts/2026/10/21/critical-vulnerabilities-php-require-immediate-patching
- UptimeRobot, “Inside PHP2Shell: Why websites took themselves offline”: https://uptimerobot.com/knowledge-hub/reports-research/inside-php2shell-why-websites-took-themselves-offline/
- Malwarebytes, “PHP2Shell: Why many websites had to go offline” (Oct 21, 2026): https://www.malwarebytes.com/?p=479720
- SecurityWeek, “PHP2Shell exploitation started days before patches”: https://www.securityweek.com/php2shell-exploitation-started-days-before-patches/
- BleepingComputer, “Amazon says PHP2Shell exploitation began 4 days before patches”: https://www.bleepingcomputer.com/news/security/amazon-says-php2shell-exploitation-began-4-days-before-patches/
- TechTarget, “PHP2Shell disclosure unravels after leaks forced early patch drop”: https://www.techtarget.com/cybersecurity/news/366652613/PHP2Shell-disclosure-unravels-after-leaks-forced-early-patch-drop
- NVD CVE API (2023–2026 CVE counts by publish date, through Oct 25, 2026): https://nvd.nist.gov/developers/vulnerabilities
- IBM X-Force, “AI can find serious vulnerabilities at unprecedented speed. Can defenders keep up?”: https://www.ibm.com/think/x-force/ai-vulnerability-discovery
- VulnCheck, “State of Exploitation 1H 2026”: https://www.vulncheck.com/blog/state-of-exploitation-1h-2026
- Patchstack, “State of WordPress Security in 2026”: https://patchstack.com/whitepaper/state-of-wordpress-security-in-2026/
- IBM Cost of a Data Breach 2026: https://www.ibm.com/reports/data-breach (key findings via eSecurity Planet: https://www.esecurityplanet.com/cybersecurity/ibm-2026-cost-of-a-data-breach-report-key-findings/)
- Anthropic, “Disrupting the first reported AI-orchestrated cyber espionage campaign” (Nov 13, 2025): https://www.anthropic.com/news/disrupting-AI-espionage
- Wordfence weekly vulnerability report, Oct 12–18, 2026: https://www.wordfence.com/blog/2026/10/wordfence-intelligence-weekly-wordpress-vulnerability-report-october-12-2026-to-october-18-2026/
- CISA Known Exploited Vulnerabilities catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- NVD, WordPress core CVE-2026-63030, CVE-2026-60137, CVE-2026-87902: https://nvd.nist.gov/vuln/detail/CVE-2026-63030, https://nvd.nist.gov/vuln/detail/CVE-2026-60137, https://nvd.nist.gov/vuln/detail/CVE-2026-87902
- NVD, CVE-2026-9082 (Drupal core): https://nvd.nist.gov/vuln/detail/CVE-2026-9082
- Drupal, SA-CORE-2026-014: https://www.drupal.org/sa-core-2026-014
- Adobe, APSB26-146 (CVE-2026-75650): https://www.adobe.com/trust/security/products/magento/apsb26-146.html and credential rotation guidance: https://experienceleague.adobe.com/en/docs/commerce-knowledge-base/kb/announcements/commerce-apsb26-146
- Sansec, SessionReaper exploitation: https://sansec.io/research/sessionreaper-exploitation
- Node.js, October 2026 security releases: https://nodejs.org/en/blog/vulnerability/october-2026-security-releases
- CISA, Shai-Hulud npm supply chain compromise (Sep 23, 2025): https://www.cisa.gov/news-events/alerts/2025/09/23/widespread-supply-chain-compromise-impacting-npm-ecosystem
- InfoQ, Axios npm supply chain compromise (Apr 2, 2026): https://infoq.com/news/2026/04/axios-supply-chain
- PHP supported versions: https://www.php.net/supported-versions.php
- Microsoft .NET support policy: https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core












