For people responsible for PHP websites and servers. Follow the security update response, find out which PHP serves your site, and compare options for an older application.
The PHP project's October 20 warning was followed by four branch releases on October 21. PHP 8.2 users also face a December end to upstream security support.
Distribution notices and package trackers identify their own fixed builds. Older releases also require attention to the maintenance service covering the package.
The October 22 update records separate control-panel releases from PHP packages supplied through different channels. Hosting teams need to confirm the runtime assigned to each site.
Read the advisory, identify the relevant package and runtime, and check the running service. Learn what a version number, installed update and process check can each establish.
Understand backported fixes, compare the full distribution package build, and distinguish command-line PHP from PHP-FPM or Apache. Investigate workers that may still be using a replaced file.
Compare an application upgrade with precisely covered vendor support and short-term exposure controls. See how support scope, compatibility, cost and recovery affect the decision.
Allow Google Analytics cookies to measure visits and use of the version checker and booking pages? Names, email addresses, notes and submitted PHP versions stay out of analytics. You can use the site with analytics off.