Skip to content

WordPress News

PHP Security Release Brings Two Higher Priority Risks for WordPress

Patchstack says most of PHP's November 2026 fixes are low reach for WordPress sites, but two issues deserve faster attention at the server level.

Source Patchstack (opens in a new tab)
Abstract server stack with shield shapes and browser windows in a calm, soft-lit editorial illustration
Illustration for this article. Generated by AI.

Patchstack reports that the PHP security release published on November 19, 2026 fixes 18 CVEs across PHP 8.5.13, 8.4.28, 8.3.37, and 8.2.36. For WordPress site owners, the main point is that these are not WordPress bugs, but host-level issues, and Patchstack says two of them are close enough to ordinary hosting setups that they should not wait for a routine update window.

The source says most of the fixed issues remain uncommon, rare, or tied to plugin-specific behavior. But it highlights one timezone cache issue and one PHP-FPM request smuggling issue as the exceptions most likely to matter on typical WordPress hosting.

What changed

The new PHP versions fix 18 vulnerabilities. Patchstack says most do not reach WordPress core, or only apply in narrow conditions such as unusual server settings, specific PHP modules, or plugins that handle remote URLs or sessions in nonstandard ways.

The two issues called out for quicker action are CVE-2026-129496 and CVE-2026-129289. The first is a timezone cache use-after-free bug that does not depend on WordPress itself. The second is a PHP-FPM request smuggling flaw that becomes reachable when the front end reuses FastCGI connections, because WordPress reads php://input on REST requests and the source says XML-RPC does the same. Patchstack also notes that session upload progress had been enabled by default until this release, but says the related session flaws still usually need a plugin to read session data back.

What it means for your website

If your site runs on managed hosting, the practical issue is whether your host has already applied the updated PHP version. A WordPress core update does not fix any of these issues, because the problems sit below WordPress in PHP and server configuration.

For most business sites, the bigger concern is server setup, not content or theme changes. The source says the timezone bug has no application-level mitigation, and the PHP-FPM request smuggling issue depends mainly on whether FastCGI connection reuse is enabled on the front end. Many of the other fixes matter only if a plugin uses remote URL wrappers directly instead of WordPress HTTP functions, or if it relies on PHP sessions.

What to do now

  • Ask your host or server admin which PHP branch and patch version your site is running, and whether the November 19, 2026 security release has been applied.
  • Confirm that this is being handled as a host-level update, because updating WordPress alone does not address these PHP vulnerabilities.
  • Have your server admin check whether FastCGI connection reuse is enabled in front of PHP-FPM, since Patchstack says that setting determines whether the request smuggling issue is reachable.
  • Review any plugins or custom code that use file_get_contents() or fopen() on remote URLs, because the source says WordPress core does not use the affected HTTP stream wrappers but plugins might.
  • Monitor plugins that start PHP sessions or share session storage, since the session-related fixes are mostly plugin territory according to the source.