Skip to content
XpansionIT
All Blogs
Custom Software and SaaS Development8 min read

PHP2Shell and WordPress: What to Do Now, and When to Move On

PHP2Shell put every WordPress site at risk and took cyber.gov.au offline. Here's what to check today, and why it may be time to move your website off WordPress for good.

Afif Alamgir

Engineering lead

  • PHP2Shell
  • WordPress security
  • PHP vulnerability
  • move off WordPress
  • WordPress to Next.js
  • website security Australia
PHP2Shell and WordPress: What to Do Now, and When to Move On

What Is PHP2Shell, and Is Your WordPress Site at Risk?

PHP2Shell is the name for two critical security flaws in PHP, the language that runs WordPress and many other websites. They let an attacker run their own code on a website's server without logging in. If your site runs on WordPress and your host hasn't installed the fixes PHP released on 21 October 2026, your site is at risk.

The fix for this flaw is a PHP update, and most good hosts have already applied it. The bigger question is what PHP2Shell says about how your website is built, and whether it's time to move to something that leaves far less open to attack.

What Happened

On 20 October 2026, details of two flaws in PHP, CVE-2026-109618 and CVE-2026-109619, leaked online before they were meant to be announced. PHP rushed out fixed versions the next day: 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Both flaws are rated 9.2 out of 10 for severity, and PHP said every installation serving web pages was at risk (watchTowr).

Australia felt it straight away. The Australian Signals Directorate's Australian Cyber Security Centre issued a critical alert on 21 October, telling organisations to find every place they run PHP and get ready to patch (Cyber Daily). That night, cyber.gov.au and other federal websites went offline (iTWire).

Attackers moved quickly. On 26 October, the US cybersecurity agency CISA added both flaws to its list of vulnerabilities being actively exploited (The Register).

Because PHP sits underneath WordPress, Drupal, Joomla, Magento and countless custom PHP sites, this wasn't a problem with one plugin or one theme. It was a problem with the foundation almost all of them stand on.

What to Check Today If You Run WordPress

Start with these, whether or not you plan to move.

  • Check your PHP version. In WordPress, go to Tools, then Site Health, then Info, then Server. You need 8.2.35, 8.3.36, 8.4.27, 8.5.12 or newer.
  • Ask your host directly. Ask whether they've patched PHP2Shell on your server, and get the answer in writing.
  • If you're on PHP 8.1 or older, treat it as urgent. These versions no longer get regular fixes from PHP. Only some hosts and Linux vendors provide patched versions, so upgrade.
  • Update WordPress, your theme and every plugin, and delete plugins you don't use.
  • Put a web application firewall in front of the site. Cloudflare released free emergency protection rules for PHP2Shell.
  • Look for signs of a break-in: admin users you don't recognise, unfamiliar files, unexpected redirects, or your host flagging unusual activity.
  • Make sure you have a recent backup stored somewhere other than the website's own server.

If anything looks wrong, contact your host and the ACSC on 1300 CYBER1 (1300 292 371).

The Bigger Lesson: It's Not Just About PHP

It would be easy to blame PHP, but that misses the point. PHP fixed the flaw within a day. Every programming language and framework has serious flaws from time to time. In December 2025, for example, a flaw nicknamed React2Shell affected React Server Components, including Next.js, the framework we build most websites with. It was patched quickly too.

The real difference is how much of your website is exposed, and who is responsible for keeping it patched.

A typical WordPress site runs PHP code on the server every time someone visits a page. It usually depends on a theme and ten, twenty or more plugins, each written by a different developer, each needing its own updates. And on most small business sites, nobody is clearly responsible for applying those updates, or for checking that the host has. That's a lot of doors, and nobody watching them.

A well-built custom website can shut most of those doors:

  • Fewer moving parts. No plugin marketplace. Only the code your site needs.
  • Pages served as ready-made files. Many pages can be built in advance and served from a global network, so no server code runs when someone reads them.
  • Hosting that patches the platform for you. Managed platforms update the underlying systems themselves.
  • Someone who owns it. A developer who knows the code, watches for security alerts and applies fixes, instead of hoping each plugin author does.

Your Options

OptionWhat it meansBest forTrade-off
Harden WordPressManaged WordPress host, fewer plugins, automatic updates, firewallSimple sites with a tight budgetStill PHP and plugins, so the same risks remain
Headless WordPressKeep WordPress for editing, show pages through a separate Next.js front endTeams who like editing in WordPressTwo systems to maintain
Custom-coded siteA site built in Next.js, Node.js or Python, with a modern content editorBusinesses that rely on their site for leads or salesHigher upfront cost, then far less ongoing risk

Next.js, Node.js or Python? For most business websites, Next.js is the natural choice: fast pages, strong for SEO, and many pages can be built in advance so there's very little to attack. Node.js suits sites with lots of custom server logic, such as bookings or customer portals. Python, with frameworks like Django or FastAPI, suits sites tied to data, reporting or AI features. The language matters less than the approach: less code exposed to the internet, and someone looking after it.

When It's Time to Move On

Staying on WordPress can be fine for a simple brochure site that's well hosted and kept up to date. It's probably time to move if:

  • You rely on more than a handful of plugins to make the site work.
  • Nobody is clearly responsible for updates, or they keep slipping.
  • Your site is stuck on an old PHP version because something breaks when you upgrade.
  • Your site takes enquiries, payments or customer data, so a break-in would really hurt.
  • The site is slow, and you've added caching and speed plugins to cope.
  • You've had a security scare before.

Two or more of these is a strong sign that patching is only treating the symptom. We go deeper on the warning signs in outgrowing WordPress and moving to custom code, and compare the two approaches side by side in Next.js vs WordPress.

How a Move Works Without Losing Your Google Rankings

Moving off WordPress is safest when it's planned, not rushed after a scare.

  1. Audit what you have: every page, post, form and integration, and which pages bring in traffic.
  2. Keep your web addresses, or set up permanent redirects from every old address to its new one, so Google and your visitors follow you.
  3. Move your content into a modern editor your team can use without a developer.
  4. Rebuild the important features properly, such as forms, bookings and payments, instead of copying plugin workarounds.
  5. Launch, then watch Search Console for a few weeks to catch any missed pages or errors.

If your site also runs custom PHP software, such as a customer portal or booking system, our guide to legacy application modernisation covers your options there.

Why This Matters to Us

We're a small Adelaide team, and we spent the week after PHP2Shell answering the same question from business owners: "Is my website safe?" Most of them didn't know which PHP version their site ran on, who their host was, or who was meant to apply updates. That's not their fault. WordPress makes it easy to launch a site and easy to forget about it. We'd rather build a site with fewer weak points, keep it patched for you, and make sure you own every line of the code.

Worried About Your Website?

Send us your website address and we'll check which PHP version it runs, whether it looks exposed, and what we'd do in your position, whether that's a simple update or a move to a custom-coded site. If you decide to move, we'll give you one fixed price before any work starts, and the finished site is yours.

See how we build fast, secure websites and web applications, or send us your site.

FAQ

Questions readers ask

  • What is PHP2Shell?

    PHP2Shell is the nickname for two critical PHP flaws, CVE-2026-109618 and CVE-2026-109619, that let attackers run code on a website's server without logging in. PHP released fixes on 21 October 2026.

  • Does PHP2Shell affect WordPress?

    Yes. WordPress runs on PHP, so any WordPress site on an unpatched PHP version is at risk. Check that your site runs PHP 8.2.35, 8.3.36, 8.4.27, 8.5.12 or newer.

  • How do I check my WordPress PHP version?

    In your WordPress dashboard, go to Tools, then Site Health, then Info, and open the Server section. You can also ask your hosting provider directly.

  • Is PHP2Shell being exploited?

    Yes. Attacks were seen soon after the details leaked, and the US cybersecurity agency CISA added both flaws to its list of actively exploited vulnerabilities on 26 October 2026.

  • Should I move my website off WordPress?

    Not always. A simple, well-hosted site that's kept up to date can stay. Consider moving to a custom-coded site if you rely on many plugins, can't upgrade PHP easily, nobody owns updates, or your site handles enquiries, payments or customer data.

  • Is Next.js more secure than WordPress?

    No framework is immune; Next.js had its own critical flaw in December 2025. But a custom Next.js site usually has far less exposed to attack: no plugin marketplace, many pages served as ready-made files, and a developer responsible for patching.

Share