Stuart Neal
Director of Operations at Nextgen Marketing
We have worked with Vitalli and his team for well over a year now and will continue to do so in the future.
Having the confidence in an agency that allowed us to scale up and down development resources, as and when needed, has really made a positive difference to our agency.
Home / Blog / News / 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.
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.
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.
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