I opened my morning briefing on Wednesday, October 21, expecting the usual mix of plans for the day and software news that our AI agents put together. One item changed the morning for our team. Two critical flaws had been found in PHP, the language behind every WordPress site and much of the web. Together they were called PHP2Shell, and the reported severity was near the top of the scale.
We started by checking which of the sites we manage needed attention. Pantheon had already begun rolling out patches across its platform, so we applied patches to the sites that weren’t covered by that rollout.
By mid-morning, every site we manage had been patched. By then, clients were starting to see the news and email us about what they should do. Several were ready to take their websites offline after hearing that advice in the coverage.
We could reassure those clients because our team and providers like Pantheon and Cloudflare already had fixes and protections rolling out. What stayed with me after that morning was how quickly the flaws had been found and demonstrated, and what that pace might mean the next time an alert lands.
What PHP2Shell actually is.
PHP stands for “PHP: Hypertext Preprocessor.” It’s a programming language that runs on a website’s server, handling much of what happens behind the scenes, from retrieving content to processing forms and checking whether someone is logged in. WordPress is built on PHP, so even if you’ve never written a line of code, it’s part of what makes your website work.
PHP2Shell is the name given to two related vulnerabilities in PHP’s core engine, tracked as CVE-2026-109618 and CVE-2026-109619.1 They involve the way PHP handles memory when a request fails or when internal information is carried between requests. Under the right conditions, an attacker could exploit them without logging in.
The researchers demonstrated two possible outcomes. The first is remote code execution, which lets an attacker make a server run instructions of their choosing. The second is memory disclosure, which lets them read information from a running process. That could expose passwords, session tokens, or other data meant to stay on the server. The reported severity reaches 9.2 out of 10, in the critical range.2
A CVE, short for Common Vulnerabilities and Exposures, gives everyone a shared identifier for a reported flaw. The severity score helps a provider decide how urgently to act. Whether your own site was attacked is a separate question. Applying the patch addresses the vulnerability, while reviewing logs can help your provider look for earlier signs of compromise and explain what the evidence shows.
CBC News’ Andrew Chang has a good explainer on the discovery, its reach, and the role AI played. It is worth eight minutes of your time.
The fix arrived in PHP 8.2.35, 8.3.36, 8.4.27, and 8.5.12, with some vendors supplying patched builds for older branches.3 On October 23, PHP’s maintainers followed up with a recommendation to disable a feature called session upload progress pending a further fix for an unusual configuration.4 Follow-up advisories are normal. Someone has to be reading them.
When everyone is looking.
PHP powers roughly seven in ten websites whose server-side language can be identified,5 and it has done that job, successfully, for decades. Some of the affected code had been in place for more than ten years. Finding the flaws required researchers to work through subtle interactions deep within PHP’s engine. They used advanced AI models to uncover the weaknesses, build working demonstrations, and adapt them across applications. The researchers describe an overall effort that took one person a week rather than a specialist team months, with working exploits adapted across applications in hours.6 This is not a bug caused by careless coding or a neglected project. It is the kind of deep, subtle flaw that can remain hidden in mature software. PHP’s massive scale makes it an obvious priority for this kind of research. A single discovery can affect millions of websites.
That scrutiny is part of the business case for PHP. When software runs so much of the web, there’s a strong incentive to find its flaws and get them fixed. Here, researchers at cloud security company Wiz worked with OpenAI, PHP’s maintainers, and infrastructure providers on fixes and temporary protections ahead of public disclosure. By the time the story reached the news, patches were already rolling out.7 Less widely used platforms don’t attract the same investment in security research. Their flaws can remain undiscovered for longer, and whoever eventually finds them may have very different intentions.
PHP has no shortage of critics, and WordPress gets many of the same criticisms by extension: slow, bloated, insecure. If PHP2Shell sounds like another reason to say, “That’s WordPress for you,” consider how the flaws were found. AI is changing the pace of security research, and every platform will have to reckon with that.
This isn’t really a PHP issue.
PHP2Shell has plenty of company. Some of the most serious security incidents of the past fifteen years have affected entirely different languages, products, and platforms:
- Log4Shell (December 2021). A flaw in Log4j, a Java logging library embedded in an enormous range of enterprise software, scored a perfect 10 out of 10 and set off a global patching scramble that ran for months.8
- Microsoft Exchange ProxyLogon (March 2021). Tens of thousands of email servers were compromised, many of them before their owners knew a patch existed.9
- MOVEit Transfer (May 2023). A flaw in a file-transfer product used by governments and large institutions led to large-scale data theft.10
- Drupalgeddon (October 2014) and Drupalgeddon2 (March 2018). For the 2014 incident, Drupal’s security team advised that any site not patched within seven hours of the announcement should be assumed compromised.11
- Next.js middleware authorization bypass (March 2025). A critical flaw in one of the most popular modern JavaScript frameworks allowed attackers to bypass authorization checks implemented in middleware.12
- React Server Components (December 2025). A critical flaw in React’s server rendering affected specific server packages and frameworks and required teams to track down where the affected code was running.13
Then there’s the XZ Utils backdoor, discovered in March 2024. An attacker gained trust within an open-source project and inserted malicious code into a compression library used by Linux distributions. The backdoor could compromise secure remote access on affected systems. Developer Andres Freund uncovered it while investigating unusually slow logins, before the compromised versions reached widespread production use. The warning sign was a small performance problem. Someone paying attention made the difference.
The incidents affected everything from enterprise email to frameworks often recommended as alternatives to WordPress. A different platform changes what you need to protect, so someone still has to know what’s running, follow advisories, apply fixes, and check that they worked.
The clock is faster now.
For many vulnerabilities, teams could count on some time between public disclosure and widespread attacks. Turning research into a working exploit took skill and time, which gave providers room to fit patches into routine maintenance. Even then, some flaws were exploited within hours or before a patch was available.
PHP2Shell is the clearest signal yet that the gap is closing. The researchers’ use of AI also shows how similar tools could help attackers find and exploit flaws faster. Cloudflare reported attack traffic adapting as its protections were deployed, which tells you how quickly methods change even if it does not tell you who, or what, was behind each request.14 Pantheon’s early notices described probing at the platform level. On the sites we manage, which sit behind Cloudflare’s protections, we found no evidence of anything reaching them. That is the system working, and it is not a reason to relax.
Drupal’s seven-hour warning in 2014 sounded alarming at the time. I think it’s a reasonable baseline now, and it changes what a provider needs to have ready before an alert arrives. On Wednesday, we already knew which software our sites were running, how to update it, and who was responsible. We also had hosting partners and a firewall in place, so we could spend the morning patching and checking sites.
I also used AI to read the advisories against our inventory, cross-check which sites were affected, and work through the updates faster. Once the patches were in place, our team verified each environment and tested the features people depend on. That mix of fast tools and accountable people is what I think good maintenance looks like from here on.
What is at stake is trust.
It’s easy to talk about scores and patches until you’re the person explaining to members why their information was exposed.
Over the years, organizations have come to us for help with hacked websites. Some had compromised plugins, while others relied on abandoned themes or code nobody had maintained in years. Once the site was working again, the harder work was dealing with the disruption and rebuilding trust.
Picture it for an association. Renewal season opens and the payment form is quietly sending card details somewhere else. Or the member directory is replaced with pharmacy spam and a member notices before you do. Or your database, with every member’s name, email, and employer, is for sale. Now you are drafting the notification letter. You are explaining to the board how long it was happening. You are answering the question every member is thinking, which is whether they can trust you with their information next year.
For a regulator it is sharper still. The public register is the one thing the public needs from you, and the one thing a licensee needs to prove they are in good standing. If it goes offline, or worse, if someone can change what it says, your credibility is the thing on the line. Nobody writes an angry letter about the server. They write it about you.
I am glad to say that in all the years we have been doing this, no website under our active management has been hacked. I am not saying that to boast. I am saying it because the difference between the sites we have repaired and the sites we have protected has never been the platform. It has been whether someone was responsible for watching.
What to expect from your web provider.
As security threats move faster, organizations need practices they can rely on. That includes knowing what their suppliers are responsible for, how quickly they will respond, and what happens when something goes wrong. A security alert shouldn’t be the first time you have that conversation.
A service level agreement, or SLA, puts those expectations in writing. It should be something clients can understand and use, with practical answers about support, maintenance, and security.
Our Service Level Agreement sets out those responsibilities for each service we offer. For a suspected compromise, our initial response target is four hours on a Maintenance Plan and two hours on a WebOps Retainer, measured during support hours. That means acknowledging the issue, assessing its priority, and confirming the next steps. Resolution time depends on what we find. We also aim to assess critical patches within one business day of release, taking severity and exposure into account.15
Whatever provider you use, you should be able to get answers to four questions without becoming a PHP specialist:
- Was our site affected? What needed attention, and who was responsible for updating it?
- Has the fix reached our site? What was installed, when, and how was it checked?
- Are our important services working? Were forms, renewals, registrations, and other essential functions tested after the update?
- Is there any follow-up? Are further updates, log reviews, or site-specific checks still needed?
Who answers those questions depends on what your provider looks after. A managed host may update PHP and protect the infrastructure, while responsibility for WordPress, plugins, themes, and custom code sits with whoever maintains your website.
That maintenance includes applying updates, checking for security issues, and testing that supported features still work. Even when WordPress and its plugins are current, custom code can age. Replacing unsupported components or improving older integrations takes development time beyond routine updates.
That’s where an ongoing development arrangement, such as our WebOps Retainer, gives clients room to plan improvements alongside maintenance. It helps protect the investment already made in the website by addressing ageing code and changing needs before they turn into urgent problems. The scope matters here: clients should know what their plan covers, what needs a separate budget, and who is responsible for identifying the work.
An SLA can tell you who is responsible and how quickly they’ll respond. Keeping an inventory, maintaining access, and practising the update and testing process are what let a team follow through when the alert arrives.
Security is a decision, not a feature.
I remember PHP2Shell as a good week because the preparations held. We patched the sites we manage, and most of our clients heard about it from our email before they saw it in the news.
That outcome depended on decisions made well before Wednesday about who would host our sites, how we would protect them, and who would keep the software inventory current and look after the sites every month, including the quiet ones.
Most of the organizations we work with made those decisions years ago. A few are still on hosting-only arrangements, where the server is maintained and the website software is not, and this week was a reminder of what that gap actually means. Moving from basic maintenance to a WebOps arrangement is, in the end, a decision about how much of this you want to be your problem. The websites that fared best this week were the ones whose owners had decided it should be ours.
The pace is not going back to what it was. The tools that found PHP2Shell will find the next one, and the next one may not be in PHP. Whatever platform you run, somebody needs to be watching it, and they need to be ready before the alert lands. That is what maintenance is for. For our clients, it is what they have been paying for all along.
Sources and advisories referenced in this article.
- PHP security team, Security advisory: Critical remote code execution vulnerabilities, update now (21 October 2026). CVE-2026-109618 and CVE-2026-109619. The detailed advisories are RCE via OOM corruption and RCE via stale global state. ↩︎
- PHP security team, Upcoming Critical PHP Security Release (20 October 2026). Both vulnerabilities are rated CVSS v4.0 9.2. Wiz Research’s PHP2Shell research report describes the demonstrated remote code execution and memory disclosure. ↩︎
- PHP security team, 21 October 2026 security advisory. Lists PHP 8.2.35, 8.3.36, 8.4.27, and 8.5.12, plus vendor patches and source backports for older branches. ↩︎
- PHP security team, Informational advisory: Session upload progress (23 October 2026). Describes the unusual serializer configuration and interim mitigation for CVE-2026-115560. ↩︎
- W3Techs, Usage statistics of PHP for websites. The report dated 11 November 2026 records 68.8% of websites whose server-side programming language W3Techs identifies. The source updates daily and does not measure all websites, applications, or internet traffic. ↩︎
- Wiz Research, PHP2Shell research report, 21 October 2026. Reports exploit adaptation across applications in hours, and the overall research effort taking one researcher a week rather than a specialist team months. ↩︎
- OpenAI, Patch the Planet: global response coordination as agents uncover critical vulnerabilities, 21 October 2026; The PHP Foundation’s account of the security release. ↩︎
- Apache Logging Services, Log4j security advisory for CVE-2021-44228 (Log4Shell, December 2021). The advisory records a CVSS 3.1 score of 10.0. ↩︎
- Microsoft, HAFNIUM targeting Exchange Servers with zero-day exploits, 2 March 2021; NCSC account of the Exchange compromises. ↩︎
- CISA and FBI, CL0P exploitation of MOVEit Transfer, CVE-2023-34362, June 2023; UK NCSC, MOVEit vulnerability and data extortion incident. ↩︎
- Drupal Security Team: PSA-2014-003, 29 October 2014, including the seven-hour warning for Drupal 7; SA-CORE-2018-002, 28 March 2018, CVE-2018-7600 (Drupalgeddon2). ↩︎
- Next.js maintainers, Authorization Bypass in Next.js Middleware (21 March 2025), CVE-2025-29927. Confirms that the bypass applies to authorization checks implemented in middleware. See also the NIST vulnerability record. ↩︎
- Canadian Centre for Cyber Security, React Server Components alert, 4 December 2025. CVE-2025-55182 affects specific React server packages and frameworks using them. ↩︎
- Cloudflare, protections against PHP2Shell, 21 October 2026, updated 23 October. Describes WAF deployment and attackers changing payloads to try to bypass protections. ↩︎
- Twirling Umbrellas, Service Level Agreement, effective 8 November 2026 (checked 10 November 2026). Sections 3, 5, and 6 cover response targets, critical patch assessment, and security incidents. ↩︎
