On 18 November, the PHP security team announced critical PHP fixes for 19 November 2026, covering all branches still supported. This alert concerns businesses whose website or applications use PHP, the software that runs their code on the server. We recommend preparing a rapid intervention, giving priority to exposed configurations and to the functions essential to your business.
Critical PHP patches: what does this announcement change?
According to PHP's announcement, the most serious vulnerabilities require a configuration that differs from the default settings or an uncommon installation. The CRITICAL label indicates the maximum announced severity, without meaning that every site meets the same attack conditions. To decide the order of interventions, ask for a comparison between the conditions described in the technical advisory and the settings of each server.
The PHP team plans to publish the technical details and the numbers of the fixed versions together with the updates. Prepare your tracking with two separate pieces of information: the installed version and the fixed version to apply. Avoid signing off an intervention on the sole statement “PHP is up to date”.
What are the consequences for your shop or your applications?

Take an online shop as an example. To prepare its update, list in the inventory the shop site, its administration and the processes that send orders to accounting. Add the forms and the exchanges with payment or delivery services.
Next, ask the technical team to list the PHP version used by each of these components. Include the PHP-FPM services, which run the sites’ requests, as well as the Docker images, the templates used to build application containers. For a server shared between several sites, record the settings specific to each site.
Also plan a check of the distribution channel. In your follow-up, distinguish the release by PHP from the availability of the installable package in Plesk, the system repositories or at the host. Do not close the task on a simple availability announcement: ask for the version actually running after the intervention.
For the shop, define a precise business validation: place a test order, find its payment and check that it has been passed on. Plan for someone able to recognise an order anomaly, with access to the admin area. Give them a slot in the maintenance schedule.
Do you need to move to PHP 8.6 to protect yourself?
PHP also announces PHP 8.6 for 19 November. This new version introduces behaviour changes and deprecations, meaning features whose use is gradually being phased out. WordPress notes in particular compatibility work in its development and deprecated functions present in plugins.
Apply the fix that matches your branch, as long as it is still supported. Treat the move to PHP 8.6 as a separate operation, after validating WordPress, the theme, the plugins and any custom code. Our news article on WordPress and PHP 8.6 compatibility tests supports this preparation.
To organise the security intervention, appoint a deployment lead and a person responsible for validating that everything works. Set a deadline based on the exposure established by the technical advisory. If a dependency blocks the update, record the blocker, its owner and the next planned check.
Which checks should you ask your team for?
-
Which version fixes our installation? Have the full version number recorded before any intervention, then match it against the official advisory. Ask which settings make the site affected and which package brings the fix. Keep these details in the maintenance record, along with the list of sites handled.
-
How do we restore service if it fails? Prepare a backup of the files and the database, along with a server snapshot where the environment allows it. Check the access needed for the restoration. For the shop, define how to preserve the orders received since the backup.
-
Which checks complete the intervention? Have the update applied and the relevant services restarted, depending on the installation. Then check the active version, payment, forms, scheduled tasks and exchanges between applications. Examine the error logs and note the test results before closing the task.




