Web Design & Development

•

9 min

PHP2Shell: Your WordPress Has a Problem No Plugin Update Can Fix

PHP2Shell: Your WordPress Has a Problem No Plugin Update Can Fix

PHP2Shell: Your WordPress Has a Problem No Plugin Update Can Fix

PHP2Shell shows how vulnerable even well-kept WordPress sites are. We explain what happened, which systems will carry you through the next five years and how to move to Framer without a redesign.

PHP2Shell shows how vulnerable even well-kept WordPress sites are. We explain what happened, which systems will carry you through the next five years and how to move to Framer without a redesign.

Olivia Ulbing-Sommeregger

by Olivia Ulbing-Sommeregger

Woman with glasses checking a website on her laptop, stock image for the PHP2Shell security flaw

In a nutshell

  • PHP2Shell is two critical flaws in PHP itself (CVSS 9.2) that allow code execution without a login.

  • A WordPress, theme or plugin update won’t help, only a PHP update to 8.2.35, 8.3.36, 8.4.27 or 8.5.12.

  • A good five hours passed between the leak and the first attacks, and around 79% of PHP services run on unsupported versions.

  • For company websites from 2026 to 2031 we recommend hosted systems like Framer, and Shopify for shops.

9.2

9.2

9.2

out of 10 points: CVSS score of both PHP flaws

out of 10 points: CVSS score of both PHP flaws

~5 hrs

~5 hrs

~5 hrs

between the leak and the first attacks

between the leak and the first attacks

79%

79%

79%

of identifiable PHP services run without support

of identifiable PHP services run without support

39.6%

39.6%

39.6%

of all websites run on WordPress (W3Techs)

of all websites run on WordPress (W3Techs)

This week PHP2Shell is showing what happens when it’s not the facade that wobbles but the foundations. On 21 October 2026 the PHP team released emergency updates outside its normal schedule because two flaws (CVE-2026-109618 and CVE-2026-109619, both CVSS 9.2 out of 10) let attackers run code without logging in. This doesn’t affect a plugin or a theme. It affects PHP itself, the language that, according to W3Techs, runs 69.3% of websites with a known server-side language. With 39.6% of all websites, WordPress is the biggest passenger on board. In plain English, the update button in your dashboard won’t help this time. We’ll explain in simple terms what happened, whether PHP is still fit for purpose in 2026 and which systems will carry you through the next five years.

As of 22 October 2026. The situation is still developing, and we’ll update this post as soon as reliable figures on actual attacks are available.

What actually happened with PHP2Shell?

Imagine someone finds a master key for every house on the street, and not for your flat door but for the lock in the foundations. That’s exactly how PHP2Shell works. Security researchers at Wiz Research found two bugs in PHP that let strangers run their own commands on your server without logging in. According to Malwarebytes, the malicious code then runs with the rights of the PHP process. Stealing data, changing content, installing a backdoor, all of it is possible.

The timeline reads like a thriller. Here it is, according to Recorded Future.

  • 19 August 2026: Wiz discovers the first flaw and reports it privately to the PHP security team on 24 August.

  • 20 October: PHP announces an unscheduled release for 21 October at 14:00 UTC.

  • 21 October, 02:29 UTC: An archive of leaked information appears on VirusTotal.

  • 21 October, 07:34 UTC: Patchstack reports the first active attacks from hosting partners, before the patch is even out.

  • 21 October, 13:52 UTC: PHP publishes the fixes (8.2.35, 8.3.36, 8.4.27 and 8.5.12), slightly earlier than planned.

The catch is that, according to Recorded Future, it isn’t yet proven how many systems were actually cracked, and the reports are incomplete. What is proven is the size of the attack surface. Analysts at Modat count 4.38 million PHP services on 1.89 million hosts, and around 79% of those with a readable version are running on a PHP line that’s no longer supported. Even maintenance mode won’t save you, because PHP processes the request before WordPress even looks at it.

How could this happen?

In short, because the bug isn’t in WordPress but one level below it. According to Recorded Future, both flaws are memory errors in PHP itself. When PHP handles a request, it manages memory, frees it again and cleans up. With PHP2Shell, outdated references get left behind that point to memory that has already been freed (the experts call this use-after-free). An attacker can exploit that moment to slip in their own code.

The nasty part is that the attack strikes before your website even gets a turn. So application logs show little, according to Recorded Future, and a WordPress update does nothing, because WordPress.org itself sees no need for action on its side. What matters is the PHP version on your server, and that’s usually controlled by your host, not you.

Wiz says it didn’t just describe the attacks in theory but demonstrated them against WordPress, Drupal and Joomla. So this hits the whole PHP family. And the warning signs have been on the table for a while. According to WordPress.org statistics, 35.8% of WordPress sites run on PHP 8.1 or older, for which there’s no official fix.

“The problem isn’t the language, it’s the effort. The more responsibility for servers, plugins and updates sits with you, the bigger the risk.”
— Olivia Ulbing-Sommeregger, Founder oha! digital

This week PHP2Shell is showing what happens when it’s not the facade that wobbles but the foundations. On 21 October 2026 the PHP team released emergency updates outside its normal schedule because two flaws (CVE-2026-109618 and CVE-2026-109619, both CVSS 9.2 out of 10) let attackers run code without logging in. This doesn’t affect a plugin or a theme. It affects PHP itself, the language that, according to W3Techs, runs 69.3% of websites with a known server-side language. With 39.6% of all websites, WordPress is the biggest passenger on board. In plain English, the update button in your dashboard won’t help this time. We’ll explain in simple terms what happened, whether PHP is still fit for purpose in 2026 and which systems will carry you through the next five years.

As of 22 October 2026. The situation is still developing, and we’ll update this post as soon as reliable figures on actual attacks are available.

What actually happened with PHP2Shell?

Imagine someone finds a master key for every house on the street, and not for your flat door but for the lock in the foundations. That’s exactly how PHP2Shell works. Security researchers at Wiz Research found two bugs in PHP that let strangers run their own commands on your server without logging in. According to Malwarebytes, the malicious code then runs with the rights of the PHP process. Stealing data, changing content, installing a backdoor, all of it is possible.

The timeline reads like a thriller. Here it is, according to Recorded Future.

  • 19 August 2026: Wiz discovers the first flaw and reports it privately to the PHP security team on 24 August.

  • 20 October: PHP announces an unscheduled release for 21 October at 14:00 UTC.

  • 21 October, 02:29 UTC: An archive of leaked information appears on VirusTotal.

  • 21 October, 07:34 UTC: Patchstack reports the first active attacks from hosting partners, before the patch is even out.

  • 21 October, 13:52 UTC: PHP publishes the fixes (8.2.35, 8.3.36, 8.4.27 and 8.5.12), slightly earlier than planned.

The catch is that, according to Recorded Future, it isn’t yet proven how many systems were actually cracked, and the reports are incomplete. What is proven is the size of the attack surface. Analysts at Modat count 4.38 million PHP services on 1.89 million hosts, and around 79% of those with a readable version are running on a PHP line that’s no longer supported. Even maintenance mode won’t save you, because PHP processes the request before WordPress even looks at it.

How could this happen?

In short, because the bug isn’t in WordPress but one level below it. According to Recorded Future, both flaws are memory errors in PHP itself. When PHP handles a request, it manages memory, frees it again and cleans up. With PHP2Shell, outdated references get left behind that point to memory that has already been freed (the experts call this use-after-free). An attacker can exploit that moment to slip in their own code.

The nasty part is that the attack strikes before your website even gets a turn. So application logs show little, according to Recorded Future, and a WordPress update does nothing, because WordPress.org itself sees no need for action on its side. What matters is the PHP version on your server, and that’s usually controlled by your host, not you.

Wiz says it didn’t just describe the attacks in theory but demonstrated them against WordPress, Drupal and Joomla. So this hits the whole PHP family. And the warning signs have been on the table for a while. According to WordPress.org statistics, 35.8% of WordPress sites run on PHP 8.1 or older, for which there’s no official fix.

“The problem isn’t the language, it’s the effort. The more responsibility for servers, plugins and updates sits with you, the bigger the risk.”
— Olivia Ulbing-Sommeregger, Founder oha! digital

✓ Do’s

  • Get PHP onto a patched version
    Only 8.2.35, 8.3.36, 8.4.27 or 8.5.12 (or newer) close the flaw. Everything else is hope.

  • Hold your host to it in writing
    “It’s planned” isn’t good enough. Get confirmation that the fix is installed on your server.

  • Check server logs, not just WordPress
    The attack runs below the application. If in doubt, rotate your credentials.

✕ Don’ts

  • Relying on the WordPress update
    The flaw is in PHP, not in WordPress, your theme or plugins. The update button won’t help this time.

  • Thinking maintenance mode protects you
    PHP processes the request before WordPress even looks at it.

  • Sticking with PHP 8.1 or older
    There’s no official fix for these versions, and that won’t change.

What is PHP and why does half the web run on it?

PHP is the programming language that works in the background of a website. Your browser requests a page, PHP assembles it on the server in seconds from text, images and database entries and sends back the finished result. No PHP means no blog post, no shopping basket and no login in classic systems like WordPress, Drupal, Joomla or Magento.

It was invented by Rasmus Lerdorf. According to Wikipedia, he started writing small programs in 1993 to maintain his personal homepage and announced the first version as “Personal Home Page Tools” on 8 June 1995. Hence the name, which was later reinterpreted as “PHP: Hypertext Preprocessor”. A lot has happened since then, from PHP 3 (1998) and PHP 5 with its object-oriented model (2004) to PHP 7 with a big jump in speed (2015) and PHP 8 with a JIT compiler (2020). So the language is 31 years old and today, according to W3Techs, runs on 69.3% of websites with a known server-side language.

Why do so many systems build on it? Because back then PHP had everything the early web needed. It’s free, every cheap host supports it, you don’t need your own server landscape, and once you have a plugin ecosystem, you stay put. The result is a huge network effect. WordPress alone is behind 39.6% of all websites.

Transparency, because it belongs here: Until a few months ago we at oha! digital built all our websites on WordPress. We were fans of the system for years and recommended it to our clients with a clear conscience. For a long time it was also the right recommendation. Our switch to Framer isn’t a reckoning with the past but the result of what we’ve seen in projects, and PHP2Shell has now added the fitting exclamation mark.

What do PHP systems give you and what do they cost you?

Advantage

Disadvantage

Costs

Free software, cheap hosting

Maintenance, plugins and security are ongoing costs

Freedom

Huge plugin ecosystem, almost anything can be built

Every plugin is one more possible door

Reach

Lots of agencies, lots of know-how, easy to move

Its popularity makes it the biggest target for attackers

Operation

Full control over server and data

You (or your host) are responsible for updates, backups and security

Technology

Mature, 31 years of experience

Legacy baggage, with many sites on outdated PHP versions

The fourth point is the decisive one. With PHP systems, running them comes with the territory, just as servicing comes with a car. That works as long as someone applies updates consistently. Practice looks different. According to the Modat figures at Recorded Future, around 79% of identifiable PHP services run on a version without official support, and PHP 7.4 alone accounts for 878,761 services. A language that’s so widespread and at the same time so badly maintained inevitably becomes a permanent target.

Is PHP still fit for cybersecurity and AI in 2026?

You have to separate two things. The language PHP isn’t dead. It’s actively maintained, PHP 8.5 has been the current version since 2025, and the fixes came one day after the announcement. The operating model behind it is the problem, meaning a website that you or your host looks after on a server, with dozens of plugins that all need patching.

Cybersecurity: According to Recorded Future, a good five hours passed between the leak (02:29 UTC) and the first reported attacks (07:34 UTC). The patch window in which you can calmly take action has practically disappeared. If you look after your website by hand and by calendar, you’re no longer in the same league as the attackers in 2026. On top of that, if your host doesn’t patch immediately, there’s little you can do as a customer. That’s why, according to Malwarebytes, websites are temporarily going offline this week.

AI readiness: PHP isn’t worse here, but the systems built on it are more sluggish. AI visibility (ChatGPT, Gemini, Claude and co. as new ways of searching) demands fast, clean, well-structured pages, and today’s tools build AI directly into page building. Framer, for example, offers Wireframer and Workshop as AI features for layouts and components, and Shopify presents products directly in ChatGPT, Perplexity and Microsoft Copilot. All of this is possible in WordPress too, but usually only with extra plugins that need maintaining in turn.

Our verdict: For a company website that should be secure, fast and visible to AI from 2026 to 2031, a self-hosted PHP system is no longer the first choice. That’s not down to the language but to the effort. The more responsibility for servers, plugins and updates sits with you, the bigger the risk.

Which systems will last the next five years?

The answer depends on who you are. A corporation with its own development team needs something different from a trade business with five subpages. What the candidates below have in common is that they run as a hosted platform or modern architecture, you don’t operate your own PHP server, and AI is part of the toolbox.

System

Suits

Strength

Framer

SMEs and brands that want a stylish, fast website without technical baggage

Design freedom, AI features in the editor, hosting included

Webflow

Marketing teams with design know-how

Visual development with CMS, not built on PHP according to the Webflow Trust Center

Headless setups with Sanity or Storyblok plus Astro or Next.js

Large companies with a development team and many channels

Full control, content for web, app and AI channels from one source

Wix or Squarespace

Very small websites and DIYers

Quick start, little maintenance, but limited customisation

Shopify

Online shops of any size

See next section

Framer in detail: Framer is our favourite, and not out of convenience. You build visually, and according to TechRadar the AI features have been available to all users since May 2025 (Wireframer for page structures, Workshop for your own components in the style of your website). SSL certificates are set up automatically on custom domains, as Framer documents, and Framer also describes active DDoS protection. There’s no server for you to patch and no plugin jungle. For us that means less maintenance, less attack surface and more time for content and marketing.

And what about online shops – does Shopify have a future?

For e-commerce our answer is yes. Shopify is a hosted shop system, so you don’t maintain your own server, and the platform is evolving remarkably fast. According to The Fintech Times, Shopify presented over 150 new features with its Winter ’26 Edition on 10 December 2025. Two of them show where this is heading.

  • Agentic Storefronts: Merchants can place their products directly in conversations with ChatGPT, Perplexity and Microsoft Copilot. If you don’t show up there, you’re missing from where people are increasingly searching.

  • Sidekick: The AI assistant proactively suggests tasks, edits themes by voice command and builds admin apps from natural language.

The demand is there. In Shopify’s own Holiday Retail Report 2025, according to the same source, 66% of consumers want to use AI for at least part of their Christmas shopping. That’s a vendor figure rather than a neutral one, but the direction is right.

The catch is the same as with any website builder. Ongoing platform costs and app dependencies are part of the deal, and without clean product data even the best AI achieves nothing. That’s exactly where we come in. oha! digital is a Shopify partner and happy to help you build your shop, from setup and design to product data and performance campaigns.

What should you do now?

In plain English, if you run a PHP website you now have two jobs, closing the acute flaw and answering the platform question honestly.

Today

Check your PHP version

Ask your host in writing whether the fixes (8.2.35, 8.3.36, 8.4.27 or 8.5.12) are actually installed on your server and not just planned. This applies to all websites and applications on the server.

Today

Replace old PHP versions

On PHP 8.1 or older? Then there’s no official fix. Test on a copy and switch to a supported version, and Digidop recommends PHP 8.3 or 8.4.

This week

Look at logs from 20 October onwards

Recorded Future advises this because the attack runs below the application and is barely visible there. If in doubt, rotate your credentials.

This week

Take inventory of everything

Which websites, landing pages, shops and tools run on PHP, whether with you or with service providers? Forgotten test sites and old sites count too.

This month

Decide on your platform strategy

Ask yourself how many hours a year updates, plugins and security cost you. Small and medium-sized businesses can skip server maintenance with Framer or Webflow, large companies should look at headless architectures, and shop owners should look at Shopify.

This quarter

Plan the migration, don’t suffer it

If you only move after the next incident, you pay for it in stress and haste. Switching on your own terms is cheaper and leaves room for clean SEO redirects.

And what about the WordPress sites we still look after?

For new projects we build on Framer, and we no longer touch WordPress. That doesn’t mean we’re leaving our existing clients out in the rain. The sites still running on WordPress with us are serviced regularly, updates arrive promptly, and hosting is with Hostprofis. That’s exactly what makes the difference in an incident like PHP2Shell. If you look after your installation, you have an update to deal with the day after the news. If you don’t, you have an emergency.

In plain English, a well-kept WordPress site isn’t a security risk per se in 2026. A forgotten one is. If you don’t know when your site was last updated, that’s your answer to the question of whether you need to act.

Talk to us if you’d like a second opinion or a migration plan. We’ll look at your current site and tell you honestly whether a switch is worth it.

Free · 30 minutes

Free · 30 minutes

Is your website affected by PHP2Shell?

We’ll look at the PHP version, hosting and plugins of your website and tell you what to do now. Would you rather stay on WordPress? That’s fine too. We’ll take care of updates, security and maintenance for you.

We’ll look at the PHP version, hosting and plugins of your website and tell you what to do now. Would you rather stay on WordPress? That’s fine too. We’ll take care of updates, security and maintenance for you.

By submitting, you agree that we may contact you about your enquiry.

By submitting, you agree that we may contact you about your enquiry.

Let’s talk

Still on WordPress?

We’ll move you to Framer. Fast, with no complete redesign, and your design and content come along.

We’ll move you to Framer. Fast, with no complete redesign, and your design and content come along.

More on moving

→

FAQ

Frequently asked questions about PHP2Shell

What is PHP2Shell?

PHP2Shell is the name for two critical security flaws in PHP itself (CVE-2026-109618 and CVE-2026-109619, both CVSS 9.2 out of 10). They let attackers run malicious code on a server without logging in. The PHP team released emergency updates on 21 October 2026.

Is my WordPress website affected?

Probably yes, if your server hasn’t yet been updated to PHP 8.2.35, 8.3.36, 8.4.27 or 8.5.12 (or newer). The flaw is in PHP, not in WordPress. What matters is the PHP version on your server, which is usually controlled by your host.

Does a WordPress update help against PHP2Shell?

No. Updating WordPress, your theme or plugins doesn’t close the flaw, because it sits in the PHP interpreter. Maintenance mode doesn’t protect you either, because PHP processes the request before WordPress checks it. Only a PHP update to a patched version helps.

Is PHP still secure enough for company websites in 2026?

The language is actively maintained and fixes appear quickly. The risk lies in the operating model. Self-hosted PHP systems need consistent updates for the server, PHP and all plugins. According to Recorded Future, around 79% of PHP services with a readable version run on versions that are no longer supported.

Can I move my WordPress website to Framer without a complete redesign?

Yes. oha! digital is currently moving many client websites from WordPress to Framer. It’s quick and doesn’t require a complete redesign. Beforehand we check which content and structures will be carried over.

Olivia Ulbing-Sommeregger

Written by

Olivia Ulbing-Sommeregger

Olivia Ulbing-Sommeregger

Founder & CEO, oha! digital

Olivia Ulbing-Sommeregger is founder and CEO of oha! digital, an agency for social media, performance marketing and AI based in Salzburg. Since 2018 she has been supporting companies across Austria, Germany and Switzerland – from SMEs to brands like Bankhaus Spängler and Miele Professional – with strategy, content and advertising on Meta, TikTok, LinkedIn and Google. She is co-author of the Rheinwerk book “Follow me! Erfolgreiches Social Media Marketing” (7th edition, 2025) and completed the WIFI diploma programme in CSR, ESG and sustainability management. Her standard is straight talk instead of agency blah.

← All Klartext articles

Ready when you are!

Let’s make your
digital story work.

Tell us briefly what you’re planning.
The first call is on us.