SquishPixel Blog · Site security · WordPress · Hosting and CDNs

PHP security release fixes critical flaws: what WordPress site owners should check

According to DEV Community, a PHP security release on 19 November 2026 fixes 18 vulnerabilities in PHP 8.5 and 12 to 14 in the older branches. Seven are rated critical. All seven affect PHP 8.5, five affect 8.3 and 8.4, and four affect 8.2. The fixed versions are PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36. PHP 8.1 and older get no fix because they are unsupported.

The article says the PHP security team describes the critical issues as needing non-default configuration or uncommon setups, and that no exploitation in the wild had been reported at the time of writing. The most important fix for WordPress is a request smuggling bug in PHP-FPM, the process manager that runs PHP on most hosting. It needs a web server that reuses FastCGI connections, such as nginx with fastcgi_keep_conn on, and an application that opens php://input without reading it fully. Standard nginx and Apache setups close the connection after each request and are not affected by the demonstrated attack.

Two session bugs can lead to code execution through unserialising attacker-influenced data. WordPress core does not use PHP sessions, but many plugins do. The release turns session upload progress off by default. Another critical bug involves a timezone cache and a startup warning written to PHP's error log file. A high-rated PHP-FPM privilege escalation matters for Docker setups, because the official php:*-fpm images switch on catch_workers_output and the master process runs as root.

The guide gives a five-step check: confirm your PHP version and settings, look for FastCGI connection reuse, check that session upload progress is off, make sure PHP starts without warnings, and see whether catch_workers_output is on. It also covers updating on Debian or Ubuntu, Docker and managed hosting. It notes that the official Docker images had not yet reached the fixed tags on 19 November, and that PHP 8.2 reaches end of life on 31 December 2026.

Why it matters

Every WordPress site runs on PHP, so this release affects your server whether or not you use the features involved. Most of the critical bugs need specific configurations, so your real exposure depends on how your server is set up. That is why checking settings is useful alongside updating.

Managed hosting users usually cannot update PHP themselves and depend on the host. Docker users may need to wait for fixed image tags. Anyone still on PHP 8.2 or older has a deadline to plan around, and PHP 8.1 and older get no fix at all.

The article also notes that PHP ships security updates every four weeks, so a quick, repeatable update routine is worth having.

Source: DEV Community. This brief summarises their reporting; read the original for the full detail.