Server and hosting: patching PHP properly
Plesk, cPanel, Apache, Nginx, LiteSpeed, containers: who is responsible, how do you check the real patch level, and how do you restart all workers?
Plesk Server: Checking and Patching PHP Versions
Plesk servers often run several PHP versions side by side. Here is how to check every handler, apply the PHP update and restart all workers.
Read more →02cPanel and WHM: Securing PHP
cPanel manages PHP through EasyApache 4 with separate packages per version. Here is how to check the state, restart all processes and set interim values correctly.
Read more →03Shared Hosting: What the Host Does and What You Need to Do
With shared hosting, the host patches PHP. Your job is to get the confirmation, choose the PHP version and check your website for traces.
Read more →04Securing Your Own Root Server and vServer
With your own root server or vServer, all responsibility lies with you. Here is how to check and patch PHP, restart all processes and harden the system.
Read more →05Managed Server: Clarifying Responsibility
A managed server takes a lot off your hands, but not everything. Here is how to clarify who patches PHP, who restarts and who is responsible for application, data and reports.
Read more →06Securing Apache with mod_php
The PHP team rates the risk highest for mod_php. Here is how to identify the operating mode, patch correctly, restart Apache and plan the move to PHP-FPM.
Read more →07Securing Nginx with PHP-FPM
With Nginx and PHP-FPM, security lies in pools, permissions and a clean restart. Here is how to patch after PHP2Shell and harden Nginx and PHP-FPM for good.
Read more →08LiteSpeed and LSAPI: Updating PHP
LiteSpeed uses its own lsphp packages and keeps PHP processes in memory for a long time. Here is how to apply the PHP update and make sure all processes really restart.
Read more →09Securing FrankenPHP
FrankenPHP ships PHP inside its own program. A distribution update is therefore not enough: the binary or image must be rebuilt and all workers restarted.
Read more →10php-cgi: Legacy With Risk
php-cgi often hides unnoticed in old setups, panels and on Windows. Here is how to find it, patch it after PHP2Shell and plan the switch to PHP-FPM.
Read more →11Patching PHP in Kubernetes
In a cluster, PHP lives in images. Here is how to find all vulnerable pods, rebuild images with fixed PHP, roll them out and prove the state of each workload.
Read more →12Securing PHP on Windows and IIS
Under IIS, PHP usually runs as php-cgi.exe via FastCGI. Here is how to find all installations, swap PHP safely, recycle the application pools and check the result.
Read more →Every hour counts. Write to us now.
Briefly describe your system, PHP version and observation. We will get back to you, clarify the situation and work remotely until the incident is closed and documented.