PHP released versions 8.5.13, 8.4.28, 8.3.37, and 8.2.36 on November 19. Together they fix 18 vulnerabilities. Seven are rated Critical, at 9.2 on the 10-point CVSS severity scale.

These are not WordPress bugs. They sit in PHP, the language WordPress runs on. Updating WordPress or your plugins changes nothing. Your host has to update PHP.

How likely is this to affect you?

According to Patchstack’s analysis, most of the critical bugs need unusual setups. Two are reachable on configurations that are ordinary on WordPress hosting. A third was switched on by default until this release.

  • Timezone cache bug (CVE-2026-129496): needs no login. It depends on server settings, such as a startup warning written to a file-based error log. Researchers showed code execution with it.
  • PHP-FPM request smuggling (CVE-2026-129289): WordPress’s REST API always meets the application-side condition. Exposure depends on whether your server reuses FastCGI connections, a speed setting between the web server and PHP.
  • Upload progress sessions: the session.upload_progress setting was on by default in 8.4.27 and is off in 8.4.28. Core WordPress does not read those session files. A plugin that uses PHP sessions could.

Patchstack rates the rest as rare or very rare on WordPress sites. Some only matter after an attacker already controls a plugin.

What to do

Ask your host which PHP version you run and when it will move to the patched release for your branch. Managed hosts usually handle this for you. Ask for the patched version, not just a restart.

PHP 8.1 and older are end of life and received no fixes. If you run one, you need to move to a supported version.

If you run your own server and can’t update yet, Patchstack suggests:

  • Set session.upload_progress.enabled=0 in every PHP pool.
  • Turn off FastCGI connection reuse in your web server.
  • Clear startup warnings from the error log, then restart PHP.

Also ask plugin vendors whether their code fetches remote URLs with raw PHP functions or starts PHP sessions. Those are the plugin-level places these bugs could surface.

This follows October’s critical PHP release and the server-level web server flaws we covered in the NGINX HTTP/2 story yesterday. Server software is where the serious risk is this month.


End of article