Skip to main content
October 21, 2026

PHP2Shell: What to Do Now – and When Switching CMS Makes Sense

Secure the PHP runtime first, then decide on your website: which questions matter now and when Next.js with Payload may be a suitable alternative.

By Janik Ahler
Illustration of a shield with a lock and update check for the PHP2Shell security article.

As of October 21, 2026. Technical assessment based on vendor information, not an audit of any specific website.

PHP2Shell is an urgent reason to have the PHP runtime in use checked and updated. Switching CMS is not an immediate solution. If your website is also difficult to maintain or needs a relaunch anyway, it is worth considering a suitable system afterwards. These should be separate decisions.[1][6]

What is behind the current PHP warning

On October 21, 2026, the PHP team released security updates for two critical vulnerabilities: CVE-2026-109618 and CVE-2026-109619. They may allow attackers to execute code without authentication, with the privileges of the affected web process. Security researchers at Wiz discuss these related issues under the name PHP2Shell.[1][6]

The flaws affect the handling of internal states in the PHP runtime. They are not limited to a single CMS plugin. How an attack could be carried out also depends on the specific operating environment. The report therefore means neither that every PHP website has already been attacked nor that a particular website can be considered secure without being checked.[2][3]

The PHP team recommends that all operators of PHP web applications update immediately. The warning also explicitly mentions PHP-FPM; using a different server interface alone is no reason to consider the risk resolved.[1]

What you should clarify with your hosting provider now

If you do not manage the server environment yourself, forward the official PHP warning to your hosting provider or IT service provider. Ask for specific confirmation for the environment in which your website actually runs.[1]

These questions can help:

  • Which PHP version and server package are used for my website?
  • Does this package contain the fixes for both of the vulnerabilities mentioned?
  • When were the fixes applied and the affected processes restarted?
  • Do any website functions need to be checked after the update?

For the supported PHP branches, the PHP team lists the fixed versions 8.2.35, 8.3.36, 8.4.27 and 8.5.12.[2][3] Distributions and LTS providers may supply their own packages with backported fixes. In that case, confirmation from the respective provider is what matters, rather than simply comparing a displayed version number.[1]

PHP 8.1 and older branches are outside the PHP project's regular support. For these installations, you should discuss a supported release or a package secured by the provider with that provider.[1]

Updating WordPress or a plugin does not automatically update the underlying PHP runtime. A PHP version may also serve multiple applications. Have the environment actually in use clarified rather than looking only at the visible CMS dashboard.[1][6]

Configuration changes may limit individual attack paths, but according to the PHP advisories they are not a complete substitute for the fixes. We deliberately do not recommend generic server commands here: the technical team responsible must determine the appropriate action for each environment.[2][3]

When an update is enough

If there are already signs of a breach, applying an update is not proof that the environment has been cleaned up. In that case, the IT team responsible should also investigate the incident. CISA notes that a security update alone does not fully remediate an incident that has already occurred.[7]

A working website does not need to be rebuilt because of this report. If your system suits your business, can be maintained reasonably easily and is reliably supported, the right decision may be to have the security fixes applied, check the functionality and continue running your existing website.

Separately, assess whether what you offer is still presented clearly and whether your team can update content without unnecessary steps. These are website planning questions. They should not be mixed up with the urgent task of fixing a security vulnerability.

Nor does a relaunch make sense simply because an agency prefers working with a different system. For a small website with straightforward requirements, keeping the existing solution may be the more appropriate approach.

When it is also worth considering a CMS switch

A security report may reveal that responsibility for maintaining your website has been unclear for some time. Even so, there should be concrete reasons for switching systems. We would consider these points in a review of the current setup:

Content editing: Which content do you change regularly? Can your team maintain services, project references or contact people, for example, in a clearly identifiable place?

Functions and data: Which forms, interfaces or recurring content structures does your business need? Where does duplicate maintenance or manual handover occur today?

Operations: Who handles updates, backups and errors? Has this responsibility been agreed, or will it only be clarified when the next problem occurs?

Scope: Is a targeted revision enough, is a technical migration necessary, or does the site structure no longer fit what you offer either?

The outcome may be a switch, but it does not have to be. Our website relaunch guide explains the differences between revision, migration and rebuilding. The first step here is to separate your actual needs from the current security report.

Where Next.js and Payload may be worth discussing

We see Next.js and Payload as a possible foundation for custom-developed websites. Among other things, Payload provides a content editing interface, configurable access permissions and interfaces for content and applications. The platform is based on TypeScript and can be integrated into a Next.js application.[5]

If you were to switch, we would first define which content you want to edit yourself and which structures are needed to support that. For example, maintaining recurring services or project references can be specified as a requirement before decisions are made about design and implementation. The technology should support this work, not introduce unnecessary extra steps.

The existing content, required functions and ongoing operation also need to be reviewed. Not every existing extension has to be carried over unchanged. Conversely, an important function must not disappear simply because it would need to be implemented differently in the new system.

You can find more context in the article Payload CMS: Use Cases, Costs and Website Planning. Our Payload CMS services outline how to get started with this type of website project.

A new stack still needs maintenance

Switching to Next.js and Payload is not a promise that security updates will no longer be needed. Next.js itself has published security warnings and update notices, for example on December 11, 2025, concerning issues involving React Server Components. This is a historical example of the need for maintenance, not a statement about a current vulnerability in your website.[4]

When planning a new system, we would therefore document responsibilities as well as functions: Who monitors relevant security reports? Who applies updates? Which functions are checked afterwards? And who can be contacted if an error occurs?

A review of the current setup must establish whether PHP-based services are still used elsewhere. A new frontend alone does not provide a basis for assessing the security of the entire infrastructure.

Frequently asked questions

Do I need to replace my WordPress website now?

No. First, the team responsible must establish whether the PHP environment in use contains the necessary fixes. Switching CMS is a separate decision about requirements and operations. The current warning alone does not demonstrate a need for a complete rebuild.[1][6]

Is updating plugins alone enough?

You should not rely on that. The flaws described are in the PHP runtime. Ask your provider for explicit confirmation of the fixes at this level, even if the CMS and its extensions are already shown as up to date.[2][3]

Can I wait until the relaunch to update?

That would be the wrong order. The PHP team recommends updating immediately. Have the technical team responsible address the immediate security measures and plan any potential migration separately. A future relaunch does not protect the application currently running.[1]

Are Next.js and Payload automatically more secure?

We do not make that kind of blanket statement. A different system changes the architecture and the components that need to be maintained. Maintenance and updates remain necessary there too. The documented Next.js security update shows why a stack name alone is not a sufficient assurance of security.[4][5]

Do I need to provide technical access for the initial discussion?

We do not need passwords for an initial conversation about your requirements. Describe the website you run, what you want to change and who has been maintaining it so far. This does not constitute a specific security audit or any technical implementation.

Keep, revise or rebuild your website?

If you are considering a switch independently of the current security update, we can discuss your website's requirements with you and whether Next.js with Payload is a good fit. A targeted revision also remains an option.

Discuss your project

If you are currently affected, contact your hosting provider or the IT team responsible first. Do not wait for a relaunch discussion.

Sources

[1] PHP: Critical security warning of October 21, 2026

[2] PHP: Advisory CVE-2026-109618

[3] PHP: Advisory CVE-2026-109619

[4] Next.js: Security update of December 11, 2025

[5] Payload: Official introduction

[6] Wiz Research: PHP2Shell

[7] CISA: Security updates and incident remediation