Back to AMR Softec Blog

UK PHP Security Alert 2026: What It Means for Your Website and Why Consider Next.js

Admin•
UK PHP Security Alert 2026: What It Means for Your Website and Why Consider Next.js

On 21 October 2026, the UK's National Cyber Security Centre (NCSC) issued an alert urging UK organisations to act immediately on a critical flaw in PHP, the programming language behind a very large share of websites. If your business website, online shop, booking system or customer portal runs on PHP, including WordPress, this alert is relevant to you.

This guide explains the UK PHP security alert 2026 in plain language, what the NCSC wants you to do, and how to check your own exposure. It also covers a longer-term question many business owners now ask: is it time to move from WordPress or PHP to a modern platform such as Next.js? The honest answer is "sometimes", and we explain when.

The UK PHP security alert 2026 in simple words

PHP is software that runs on a web server and builds your pages, talks to your database and handles back-end logic before a visitor sees anything. WordPress, Magento, Drupal and Joomla are all built on it, and many other products bundle it.

PHP's developers published a security update for a critical issue that may allow attackers to execute commands on vulnerable PHP servers under certain conditions. In practical terms, a successful attacker could take control of the server, and in the worst case access data held on it. No login is needed to attempt this.

What this means for a UK business:

  • Customer and business data may be at risk if a vulnerable server is compromised. Where personal data is involved, that can bring UK GDPR obligations.

  • Your website may need urgent updates, and in some cases may need to be taken offline until it is fixed. As of 22 October, press reports said a UK government minister had told the House of Lords that 32 government services were offline and four partially unavailable while the issue was dealt with (LBC).

  • You may be exposed through things you don't think of as "your website", such as hosting panels, plugins, legacy portals and third-party products that bundle PHP.

What is PHP2Shell? The technical background

The alert covers two vulnerabilities, nicknamed "PHP2Shell" in public reporting. Both are rated 9.2 out of 10 on the CVSS v4.0 severity scale.

  • CVE-2026-109618: an attacker can trigger an out-of-memory (OOM) condition in PHP. This can interrupt PHP while internal request data is only partly set up, and the cleanup that follows treats that invalid data as valid. Under certain conditions this memory corruption can be exploited for unauthenticated remote code execution.

  • CVE-2026-109619: request-owned internal state can survive after the memory behind it has been freed. A later request handled by the same PHP worker may then use that stale state before normal initialisation resets it.

The flaws sit in the PHP engine itself, not in any one website's code or plugins. So a well-written site can still be exposed if the server's PHP version is not fixed.

Who is affected?

The NCSC's guidance is deliberately broad: organisations using any version of PHP are affected, and everyone is encouraged to update to the latest fixed version. Organisations on older versions are urged to move to a fully supported release.

The PHP project published fixed releases on 21 October 2026:

  • PHP 8.5.12

  • PHP 8.4.27

  • PHP 8.3.36

  • PHP 8.2.35

PHP 8.1 and older are end of life, so there is no official release for them. The PHP team did publish source-only patches for 7.4, 8.0 and 8.1, and some Linux distributions and long-term support (LTS) vendors provide backported fixes. If you run an older version, ask your hosting provider or vendor exactly which fix you have, or plan an upgrade to a supported version.

What the NCSC recommends you do now

The NCSC highly encourages organisations to follow these priority actions:

  1. Identify every system running PHP, starting with anything internet-facing. Don't limit the search to old versions, as all versions may be affected.

  2. Update to the latest PHP version and keep monitoring for further updates. Do internet-facing systems first, then internal ones.

  3. If you can't update yet, apply the temporary mitigations published by the PHP Foundation.

  4. If you can't apply mitigations quickly, consider taking the system offline until it is fully protected.

  5. If you can't update or disable the system immediately, check it for signs of compromise, including backdoors left by an attacker, before you upgrade or mitigate. An NCSC-assured Cyber Incident Response provider can help if you lack the in-house skills.

  6. Keep monitoring third-party vendors for updates, including appliances and services that bundle PHP. NCSC-NL has published a list of software products with a PHP dependency that may be affected.

The NCSC also points UK organisations to its free Early Warning service for notifications of potential threats on their networks.

Temporary measures are not a fix

The PHP project's interim advice includes setting memory_limit=-1 (for CVE-2026-109618) and disabling session.upload_progress (for CVE-2026-109619). These reduce exposure to known attack paths but do not make a server safe. Updating PHP is the real remediation. PHP also published a separate advisory on 23 October 2026 about a configuration-dependent session upload-progress issue (CVE-2026-115560), so check php.net for the latest guidance.

Exploitation is confirmed

On 26 October 2026, the US Cybersecurity and Infrastructure Security Agency (CISA) added both CVEs to its Known Exploited Vulnerabilities (KEV) catalogue, confirming attacks in the wild. CISA's remediation deadline legally applies to US federal agencies, not UK businesses. But the listing is a clear signal that working exploits exist, so any unpatched, internet-facing PHP server should be treated as urgent.

How to check your PHP version

Log in to your hosting dashboard (cPanel, Plesk or a cloud console) and look for "PHP Selector", "System Information" or similar. If you can't find it, ask your hosting provider or IT support to confirm the exact PHP version and whether it includes the 21 October fixes. Check every environment: live, staging, and any old portals or microsites.

Why consider Next.js? The benefits for UK businesses

Patching comes first. But the alert has prompted many owners to look hard at what their website runs on, and for some, a move to Next.js is worth considering. Next.js is a React-based framework for building fast, modern websites and web applications.

  • Performance: Next.js can pre-render pages, serve them from a content delivery network (CDN), split code so visitors download less, and optimise images. Done well, this leads to faster load times, which visitors and search engines both notice.

  • SEO: pages can be delivered as fully rendered HTML, with full control over page titles, metadata, structured data, sitemaps and clean URLs. Speed and good Core Web Vitals can support search performance, although no framework guarantees rankings.

  • Scalability: static and edge delivery handle traffic spikes well, and the front end can be separated from back-end systems so each can scale and be updated independently.

  • Modern design and user experience: component-based development makes it easier to build a consistent design system, interactive features and a polished mobile experience that is easy to extend over time.

  • Reduced PHP dependency: a Next.js front end runs on Node.js rather than PHP, so it is not directly affected by PHP2Shell. But this reduces your PHP exposure only when the underlying architecture no longer relies on PHP services. If your Next.js site still pulls content from a headless WordPress site, a PHP API or a legacy portal, those PHP components still need to be patched.

An honest note on security

Next.js is not "completely secure", and no platform is. Next.js, Node.js and the npm packages a project depends on have all had their own security advisories. A Next.js site needs regular dependency updates, secure build and deployment pipelines, and sensible hosting configuration, just like any other platform.

The security benefit comes from reducing and isolating what you run, not from the framework name.

WordPress to Next.js migration: when does it make sense?

Migration is not mandatory. A properly maintained PHP or WordPress website, running a supported PHP version with timely updates, careful plugin choices and good hosting, can be secure and perfectly good for many businesses. Patching is the right response to this alert for most sites, and a rebuild should never be a panic decision.

That said, a WordPress to Next.js migration (or a move from another PHP system) is worth considering when:

  • Your site depends on end-of-life PHP, and the application or its plugins can't easily move to a supported version.

  • Updates are painful, because patching regularly breaks plugins, themes or custom code.

  • Performance and SEO are holding you back, with slow pages, poor Core Web Vitals or a heavy plugin stack.

  • You want a more modern design or a custom web application, which is hard to achieve within a theme-based CMS.

  • You run a large or growing site, or one with heavy traffic peaks, where a decoupled architecture is easier to scale.

  • You want to cut the number of PHP systems you have to defend, and keep a smaller attack surface.

You may want to stay on PHP or WordPress if your site is simple, well maintained and meets your needs, if your team relies on WordPress's editing experience, or if the budget is better spent elsewhere. A good development partner should tell you this honestly.

A phased approach often works best

  1. Now: patch PHP, check for compromise, and confirm your hosting provider's fixes.

  2. Next: audit your whole estate, including plugins, portals, APIs and any bundled PHP products.

  3. Then: decide which sites or pages justify migration, and move the highest-value or highest-risk ones first.

  4. Ongoing: maintain everything, old and new, with a regular update routine.

Considering a WordPress to Next.js migration? AMR Softec can review your current site, tell you honestly whether to patch and stay or migrate, and plan any move so your content, URLs and search visibility are protected as far as possible. Book a 30-minute consultation or contact us about Next.js development.

Next.js website development and migration with AMR Softec

AMR Softec helps UK businesses with Next.js website development, website redesign and PHP-to-Next.js migration, and also supports WordPress and PHP sites that are staying put. We start with your situation, not a sales script: sometimes the right advice is to patch and keep what you have.

  • PHP and infrastructure assessment: we find where PHP runs across your sites, hosting and integrations, and confirm patch status.

  • Patch verification and testing: we check that updates don't break plugins, checkout flows or integrations.

  • Next.js website development: custom, fast, SEO-ready websites and web applications built on Next.js.

  • Website redesign: modern, accessible, mobile-first design delivered as a maintainable component system.

  • WordPress to Next.js migration: content and structure mapping, URL and redirect planning to help protect your search visibility, metadata and structured data carried across, testing, and a managed launch.

  • Hybrid and headless stack review: security review of everything your Next.js front end connects to, including any remaining WordPress or PHP back ends.

  • Ongoing maintenance and support: dependency updates, monitoring, performance checks and security patching after launch.

Whether you need an urgent PHP check or a plan for moving to Next.js, contact AMR Softec to discuss your website.

Frequently asked questions

What is the PHP2Shell vulnerability?

PHP2Shell is the nickname for two critical PHP flaws, CVE-2026-109618 and CVE-2026-109619, that may allow unauthenticated remote code execution on vulnerable PHP servers under certain conditions. Both are rated 9.2 out of 10 and were fixed in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35.

Are all PHP websites unsafe?

No. The risk comes from running a PHP version without the fix. A site on a patched, supported PHP version, with sensible configuration and good hosting, is not exposed to these two flaws. The NCSC's message is to update promptly and check, not that PHP itself is unusable.

Is my WordPress website affected?

WordPress core does not contain these flaws, but it runs on the server's PHP engine, which does. If your host's PHP version is not patched, your site may be exposed. Ask your host to confirm the PHP version and update it, and keep WordPress, themes and plugins up to date as well.

I run an older PHP version such as 8.1 or 7.4. What should I do?

There is no official release for end-of-life branches. Ask your Linux distribution, hosting provider or LTS vendor whether they have applied a backported fix, or upgrade to a supported PHP version. If neither is possible, take the system offline or isolate it from the public internet until it is resolved.

Do I need to check whether I have already been compromised?

If a server was exposed and unpatched, yes. The NCSC advises checking for evidence of compromise, including backdoors, before or alongside remediation on systems you couldn't update quickly. If you're not confident doing this yourself, use an NCSC-assured Cyber Incident Response provider.

Is Next.js affected by PHP vulnerabilities?

A pure Next.js or Node.js application is not directly affected, because it doesn't run on PHP. But if it connects to a WordPress site, a PHP API or a legacy portal, those PHP systems still need to be patched.

Is Next.js more secure than WordPress?

Not automatically. Next.js can reduce your attack surface, for example by serving pre-rendered pages and removing plugin-heavy PHP back ends. But Next.js, Node.js and npm dependencies have had their own vulnerabilities. Security depends on how any site is built, hosted and maintained.

Do I have to migrate from WordPress to Next.js?

No. Migration is a business decision, not a requirement of this alert. Many well-maintained WordPress and PHP sites can stay as they are. Migration makes most sense when you're on unsupported PHP, struggling with performance, SEO or maintenance, or planning a redesign.

Will migrating to Next.js hurt my SEO?

A properly planned migration can reduce the risk of ranking disruption, but it can't remove it, and rankings may fluctuate after launch. A careful migration maps every URL, sets up 301 redirects, preserves titles, metadata and structured data, and checks results after launch. Planning, testing and post-launch monitoring help limit the impact, but results vary by site and no outcome can be guaranteed.

How long does a WordPress to Next.js migration take?

It depends on the size and complexity of the site, the number of integrations and how content is managed. A small brochure site is a very different project from an e-commerce or portal build. An initial assessment gives you a realistic scope and timeline.

Official references