PHP shipped 18 CVEs worth of fixes this week. Two of them reach an ordinary WordPress site

Patchstack published an analysis on 19 November of the PHP security release that went out the same day, and the useful part is the triage rather than the headline count. PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 fix eighteen CVEs between them, seven of those rated Critical at CVSS 9.2. The PHP team’s pre-announcement said the critical issues need “either non-default configuration or uncommon setups”, and for most of the list that is true. For two of them it is not — and neither is a WordPress bug, which means no plugin update, no core update and no amount of WordPress-layer hardening changes your exposure. This is the kind of thing that only gets caught when someone is tracking the PHP version under every client site rather than just the dashboard on top of it.

The two that matter this week

  • CVE-2026-129496 — timezone cache use-after-free, Critical 9.2, affects 8.2 through 8.5. This one does not care what your application does. PHP timestamps file-based `error_log` entries using the configured timezone, and on non-thread-safe builds a diagnostic logged during module startup can leave a stale pointer that FPM and mod_php workers inherit. Researchers crashed a worker on default settings and then demonstrated code execution under both FPM and mod_php with ASLR enabled. As Patchstack puts it, there is no application-level mitigation because there is no application involvement. The preconditions — a startup diagnostic plus a file-based error log — are, in their words, “a configuration a lot of sites drift into after a PHP version bump”
  • CVE-2026-129289 — PHP-FPM request smuggling, Critical 9.2, affects 8.2 through 8.5. This needs two things: the front end reusing backend FastCGI connections, and the application opening `php://input` without draining it. WordPress meets the second condition unconditionally — `WP_REST_Server::serve_request()` reads the raw body on every single REST request, and `xmlrpc.php` does the same. So reachability comes down entirely to one server setting. Exploitation can run attacker-controlled PHP as the worker user, bypass front-end routing and spoof client addresses

The rest, briefly

Patchstack walks the full eighteen and most land outside core’s reach. The two session deserialization bugs (CVE-2026-126714, CVE-2026-115560) are real, and PHP will happily write a session file for an unauthenticated visitor who POSTs the right multipart fields — but something has to read that file back with the `php` serializer, and core never calls `session_start()`. The HTTP stream wrapper issues (CVE-2026-128064, where a mixed-case `HTTPS://` URL goes out in plaintext, and CVE-2026-127960) do not touch core either, because core’s transports are cURL and a raw socket rather than `fopen()` on a remote URL. The magic-method backtrace use-after-free (CVE-2026-129474) is PHP 8.5 only and is blocked by the production INI defaults.

One deserves a mention precisely because it is post-exploitation: CVE-2026-129291, a PHP-FPM epoll use-after-free rated High at 8.8. It only matters after someone already has code execution inside a worker — which is the routine outcome of a vulnerable plugin — and it escalates that to the FPM master, usually root. It needs `catch_workers_output`, which is not the PHP default but is enabled in the official PHP-FPM Docker images.

What to actually do

  • Move every site to 8.5.13, 8.4.28, 8.3.37 or 8.2.36, whichever matches the branch. On managed hosting this is your provider’s job — ask them, and get a date
  • PHP 8.1 and earlier received nothing. They are end of life, so every CVE here that applies to 8.2 applies to them permanently. If you have inherited a client site still on 8.0 or 8.1, this release is one more line in the case for moving it
  • Turn off FastCGI connection reuse until patched: `fastcgi_keep_conn off` in nginx, or `enablereuse=off` for `mod_proxy_fcgi`. This is the single highest-value interim step for the smuggling bug
  • Set `session.upload_progress.enabled=0` administratively, per pool and virtual host. An `ini_set()` in application code is too late — the write happens before your code runs
  • Clear any startup diagnostics PHP is logging, restart the FPM master and all workers, and consider sending errors to syslog instead of a file
  • Audit plugins for the three patterns core avoids: `file_get_contents()` or `fopen()` on a remote URL instead of `wp_remote_get()`, SOAP endpoints, and anything calling `session_start()`

Why this one is awkward for agencies

The uncomfortable part of a PHP-level release is that it falls between the cracks. The client thinks the site is maintained. The maintenance covers WordPress, plugins and themes. Nobody owns the PHP version, because the host owns the server and the host is waiting for its upstream packages. On shared and managed hosting that gap can run for weeks, and the only honest answer to “are we affected” is to go and check what each host has actually shipped.

Worth being accurate about the risk, too: most of this list genuinely does need unusual configuration, and Patchstack says so plainly rather than inflating it. The two exceptions are enough on their own.

What this means for Codelibry clients

If your site is on one of our maintenance plans, we are already checking which PHP build your host is running and chasing the ones that have not shipped the update yet. Where the server is ours to configure, the interim mitigations above are going on now. Either way it will be written up in your next monthly maintenance report with the version your site ended on — there is nothing for you to chase. If you are not on a plan, this is a good illustration of what one is actually for: the problem is not in your website at all, it is one layer underneath it, and finding out requires someone to go and look.

Source: Patchstack

Vitalii Omelchenko
Founder at Codelibry and WordPress enthusiast. Helping digital agencies to protect their margins and do better at website delivery.Need help with wordpress builds? Book a call using the Contact page
our Blog

Explore our Latest Insights

WordPress core landed on the US actively-exploited list four times in 2026. It had never been there before
News
November 20, 2026
Two critical NGINX HTTP/2 flaws can reach code execution. Updating WordPress will not help
News
November 20, 2026
WordPress 7.1.5 ships 20 security fixes, including an unauthenticated path to RCE
News
November 19, 2026
whatsapp icon