PHP2Shell already struck and the calm isn’t coming back: every day your clinic’s website stays on PHP is pure anxiety
Two critical PHP flaws let attackers take over a server without a password, and the attacks started before anyone announced them. Why clinics with PHP websites should move off that technology as soon as possible.
Quick answer
PHP2Shell is a pair of critical flaws in the PHP engine that let attackers take over a server with no username or password, and attacks began before the official announcement. Every WordPress site runs on PHP; the lasting fix is moving to a pre-built architecture that runs no PHP on each visit.
Key takeaways
- PHP2Shell (CVE-2026-109618 and CVE-2026-109619) allows unauthenticated code execution on the server, and exploitation attempts began days before it went public.
- WordPress security plugins can’t stop it: the flaw is in PHP, which handles the request before the site even loads.
- PHP powers 70.2% of websites with an identifiable server language, and over a third of them run on versions that no longer get patches.
- A pre-built website (Astro or Next.js served from a CDN) has no PHP interpreter for attackers to target.
- While you migrate: get your host to confirm the patch, keep a full backup, and review access since October 17.
In this article
- What happened between October 17 and October 21
- Seven out of ten websites run on the same engine
- The security plugin you paid for can’t stop this attack
- Staying on PHP means chasing attackers forever
- A website that runs no code on each visit leaves attackers without a way in
- What your clinic needs to do before the week is out
- Frequently asked questions
While you read this, automated programs are sweeping the internet for servers with a flaw that lets a stranger get into a website and run whatever they want on it, with no username, no password, and no alert reaching anyone at the clinic. The first attempts were spotted days before the flaw was made public, and cybersecurity agencies in the UK and the EU went as far as suggesting that organizations take offline any system they couldn’t protect right away.
If your clinic’s website was built on WordPress, on a purchased theme, or as a custom project a few years back, it almost certainly runs on PHP, which is exactly the technology affected. That puts at risk the forms where patients leave their information, appointment requests, your CRM integrations, and a reputation that took years to build. The attack has already happened, and from now on every morning with your site on PHP starts with the same question: whether the next flaw is already circulating among attackers before anyone announces it, the way this one did. That anxiety lasts exactly as long as it takes your clinic to move its website off PHP.
What happened between October 17 and October 21
On October 21, 2026, the PHP team confirmed two critical vulnerabilities at the core of its engine, CVE-2026-109618 and CVE-2026-109619, known together as PHP2Shell. According to the project itself, both can allow an attacker to execute code on the server without authenticating, simply by sending a crafted web request.[1] PHP rated them 9.2 out of 10 on the CVSS v4.0 scale, and security firm watchTowr gave them the maximum score of 10.
Amazon Threat Intelligence reported that its MadPot honeypot network recorded an exploitation attempt on October 17, four days before public disclosure.[2] Cloudflare reported attack traffic starting the morning of October 21, including attempts to slip past the protection rules it had just deployed.[3] The UK’s National Cyber Security Centre (NCSC) urged organizations to consider taking offline any system that couldn’t be secured immediately, CERT-EU recommended isolating exposed applications, and Wikimedia disabled its Phabricator platform as a precaution hours before the official announcement.[4][5]
Amazon clarifies that its telemetry confirms exploitation attempts and that it can’t yet say how many succeeded, so nobody has a reliable count of compromised websites today. What has been documented is enough to worry about: attackers have been scanning for vulnerable servers with automated tools since before most administrators knew the problem existed.
Seven out of ten websites run on the same engine
PHP is the server-side language for 70.2% of websites whose language can be identified, according to W3Techs data from late August 2026.[6] WordPress, the content management system behind a huge share of clinic websites, medical blogs, and campaign landing pages, is written in PHP. According to Wiz, one of the firms that discovered the flaws, the problem reaches back to versions as old as PHP 5.4.[7]
The age of many of those installations makes things worse. The same W3Techs survey shows that 28.9% of PHP sites still run PHP 7 and 7.9% still run PHP 5, branches the project stopped maintaining years ago.[6] More than a third of websites built on PHP run on software that no longer receives regular security fixes.
The security plugin you paid for can’t stop this attack
PHP2Shell is the name given to two critical vulnerabilities in the PHP engine (CVE-2026-109618 and CVE-2026-109619) disclosed on October 21, 2026. The first exploits the way PHP handles out-of-memory errors, which can leave internal data half-initialized and later processed as if it were valid.[8] The second exploits the fact that a PHP process can reuse internal state from a previous request that points to memory already freed.[9] In both cases, an attacker without credentials can end up executing code on the server, and the affected setups include PHP-FPM, Apache with mod_php, PHP-CGI, FrankenPHP, and LiteSpeed.
Datadog Security Labs independently reproduced the flaws and confirmed that application-level authentication can’t block them, because PHP processes the malicious request before any of the website’s code runs.[10] On servers running Apache with mod_php, PHP’s technical advisory describes an attack path that fires before WordPress even loads.[8] Your security plugin, the firewall running inside WordPress, and your administrator’s strong password are all sidelined against that path.
WordPress confirmed the problem belongs to PHP and that nothing done inside the CMS will resolve it.[11] Qualys adds a detail that should alarm anyone running a clinic: researchers also demonstrated that the memory of PHP processes can be read without authentication, and that memory can contain passwords, access tokens, and API keys.[12] A leaked key can open the door to the patient records in your CRM, your messaging account, or your payment gateway. A breach involving patient information submitted through the website can also trigger legal breach-notification obligations, with the costs and reputational damage that come with them.
Staying on PHP means chasing attackers forever
The usual reaction to news like this is to ask the hosting company to update and consider the matter closed. The track record of 2026 shows why that strategy leaves a clinic in a race where it’s always a step behind the attackers. In September, just a month before PHP2Shell, the PHP project had already shipped another security round fixing eleven vulnerabilities across its four supported branches. And the 8.2 branch, still used by a significant share of PHP 8 websites, loses security support on December 31, 2026.[13]
On top of the engine sits the ecosystem. Patchstack’s State of WordPress Security in 2026 report counted 11,334 new vulnerabilities in the WordPress ecosystem during 2025, up 42% from the previous year, with 91% of them in plugins.[14] A typical clinic website stacks a theme, a page builder, a forms plugin, a booking plugin, an SEO plugin, and several more, and each one is a piece of code that runs on the server with every visit and that someone has to monitor and update without pause.
The 2026 Verizon Data Breach Investigations Report found that exploiting vulnerabilities became the leading way into data breaches, at 31% of cases, for the first time in the report’s 19-year history.[15] For a clinic, keeping a website that depends on constant patching means betting there will never be a delay, an abandoned plugin, or a flaw that attackers find first, as happened this week.
A website that runs no code on each visit leaves attackers without a way in
The alternative more and more businesses are adopting is to take the website off PHP entirely and rebuild it on a modern pre-generated architecture, also known as a static or headless architecture. In this model, pages are generated once whenever changes are published, using current tools such as Astro or Next.js, and served as finished files from a content delivery network (CDN). When a patient visits the site, the server hands over ready-made files without running an engine like PHP or querying a database exposed to the internet.
The security benefit is direct: a flaw like PHP2Shell needs a PHP interpreter answering requests, and on a pre-generated website that interpreter simply doesn’t exist. There’s also no public admin panel to hammer with password attacks and no collection of plugins executing on the server with every visit. No technology is invulnerable, and the dynamic pieces a clinic needs, such as forms and integrations, still require careful setup; the difference is that those pieces are handled by narrow, specialized services, and the surface an attacker can reach shrinks to a fraction of what a traditional WordPress installation exposes.
A clinic that makes this move also gets a faster website that’s cheaper to host and needs far less security maintenance. The website chat, where an AI receptionist answers questions and books appointments, plugs in just as it would on any other site, and patient requests flow into tools built to handle them instead of sitting in a WordPress database that few people ever review.
What your clinic needs to do before the week is out
The step that truly protects your clinic is starting the move off PHP now. That means inventorying the pages, forms, and integrations the website actually uses, preserving URLs or redirecting them carefully so you don’t lose Google rankings, and rebuilding the site on a pre-generated architecture that doesn’t depend on a server engine exposed to every new alert. Every week the decision gets pushed back is another week on the same technology that, this time, was attacked before anyone knew about the problem.
While the new website is being built, it’s enough to ask your hosting provider to confirm in writing that the emergency update has been applied and to keep a full backup of the current site.
It’s also urgent to find out whether anyone got in before October 21. Amazon recommends reviewing logs, processes, and unexpected file changes going back to at least October 17.[2] Admin users nobody recognizes, recently modified files in upload folders, or strange redirects warrant a thorough investigation and a reset of every password and API key connected to the website. Migration helps here too, because the clinic leaves behind a server that may have been tampered with and starts over on a clean foundation.
At Floix Growth, we’ve got this process covered end to end: we assess your clinic website’s current exposure and migrate it to a modern architecture without PHP, keeping your rankings and your integrations intact. If you want to know how much risk your site carries today and what the switch would look like, reach out and we’ll walk through it together using your own site’s data.
Frequently asked questions
01What is PHP2Shell?
PHP2Shell is the name for two critical vulnerabilities in the PHP engine, CVE-2026-109618 and CVE-2026-109619, disclosed on October 21, 2026. Both score 9.2 on CVSS v4.0 and can allow an attacker to execute code on the server without authenticating.
02Is my WordPress website at risk?
Every WordPress site runs on PHP, so it shares the risk from PHP2Shell and from any future flaw in the engine for as long as it stays on that technology. WordPress confirmed that updating the CMS or plugins doesn’t solve the problem, because the flaw lives on the server.
03Why move my website off PHP?
A PHP website depends on an engine and a plugin ecosystem that logged 11,334 new vulnerabilities in 2025, according to Patchstack, and PHP2Shell showed that attackers can get ahead of any fix by several days. A pre-generated architecture removes the PHP interpreter from the public server and drastically reduces what an attacker can reach.
04What technology should a clinic website move to?
For most clinic websites, a pre-generated architecture built with tools like Astro or Next.js and served from a CDN covers everything needed. Forms, chat, and booking connect through specialized services.
05Will I lose my Google rankings if I change my website?
A well-executed migration keeps existing URLs or points them to their new location with 301 redirects, preserves titles and metadata, and usually improves page speed, which is also a ranking factor. The risk comes from switching websites without planning the redirects.
References
- PHP — Security advisory: Critical remote code execution vulnerabilities (October 21, 2026)PHP (opens in a new tab)
- Amazon Threat Intelligence identifies PHP2Shell exploitation prior to public disclosure in MadPotAmazon Web Services (opens in a new tab)
- Cloudflare deploys protections against php2shell vulnerabilityCloudflare (opens in a new tab)
- NCSC (UK) — Critical security issue affecting PHPNational Cyber Security Centre (UK) (opens in a new tab)
- CERT-EU — Security Advisory 2026-018: Critical Vulnerabilities in PHPCERT-EU (opens in a new tab)
- W3Techs — Usage statistics of PHP for websitesW3Techs (opens in a new tab)
- Wiz Research — PHP2Shell: AI uncovers critical RCE vulnerabilities affecting 70% of the InternetWiz (opens in a new tab)
- PHP — Technical advisory CVE-2026-109618: RCE via OOM corruptionPHP (php-src) (opens in a new tab)
- PHP — Technical advisory CVE-2026-109619: RCE via stale global statePHP (php-src) (opens in a new tab)
- Datadog Security Labs — PHP2Shell: critical vulnerabilities in PHPDatadog Security Labs (opens in a new tab)
- WordPress.org — Critical PHP security releaseWordPress.org (opens in a new tab)
- Qualys — Media alert on the PHP2Shell vulnerabilitiesQualys (opens in a new tab)
- PHP — Supported versionsPHP (opens in a new tab)
- Patchstack — State of WordPress Security in 2026Patchstack (opens in a new tab)
- Verizon — 2026 Data Breach Investigations Report findingsVerizon (opens in a new tab)





