CVE Watch

PHP 8.3.37 and Friends: 13 Security Fixes, Four Critical, and What Reaches WordPress

· 7 min read
A WordPress site card resting on a navy server unit marked with the PHP elephant; the server holds a row of padlocked session files, one split down the middle with an amber crack, and an amber shield with a checkmark sits on its corner

Make sure your server gets the PHP security releases from November 19: 8.2.36, 8.3.37, 8.4.28 or 8.5.13. Then check two settings, because they decide how much these bugs could reach you. PHP shipped 13 security fixes in each supported branch today. Four are rated critical. Two can lead to remote code execution through PHP sessions, one through a memory bug at worker startup, and one is a request-smuggling bug in PHP-FPM that can run an attacker’s code. One of them, CVE-2026-115560, is the third PHP2Shell flaw, disclosed in October without a fix. No attacks have been reported. Most of these need a particular server or application setup, so this post is about telling whether yours has it.

At a glance

ReleasePHP 8.2.36, 8.3.37, 8.4.28, 8.5.13, all on November 19, 2026
Fixes13 security advisories: 4 critical, plus high and medium issues in FPM, PHAR, SOAP, sessions, streams and php-cgi
WorstSession file corruption (CVE-2026-126714), session serializer mismatch (CVE-2026-115560), timezone cache use-after-free (CVE-2026-129496), FPM request smuggling (CVE-2026-129289)
AffectedAll supported branches below the versions above. PHP 8.1 and older are past end of life and get no fixes
StatusNo exploitation reported

Who updates PHP?

On most WordPress sites, not you. Shared and managed hosts install PHP patch releases themselves, usually within days. Your job is to check that it happened. In WordPress, Tools → Site Health → Info → Server shows the PHP version, or from the command line:

wp eval 'echo PHP_VERSION, PHP_EOL;'

On a host with a PHP version selector, the branch is your choice and the patch level is theirs. If you’re still on a branch that’s past end of life, no patch is coming. That’s the point of treating your PHP version as a security setting. If you run your own servers, update the PHP packages and restart PHP-FPM or your web server so the workers actually load the new version.

The four critical bugs

Session bugs: only if something uses PHP sessions

WordPress core doesn’t use PHP’s built-in sessions. It keeps login state in cookies and the database. That matters, because two of the critical bugs are in sessions:

  • CVE-2026-126714, partially overwritten session files. PHP’s default files session handler didn’t clear a session file before writing a new version of it. If a write is interrupted, the file can end up holding parts of two different sessions, and the next read can turn attacker-influenced data into PHP objects. With a usable class in the application (a “gadget chain”), that becomes code execution.
  • CVE-2026-115560, session serializer mismatch. The PHP2Shell follow-up. PHP’s session upload progress feature writes data with one serializer, and a different reader can interpret part of a key as serialized object data. It needs two things on the same session storage that use different session.serialize_handler settings: two applications, two pools, or code that changes the setting at runtime. The researchers demonstrated code execution using classes from Guzzle and Monolog, two libraries many plugins bundle.

So the question is whether any plugin on your site calls session_start(). Some do, especially older form, membership, cart and captcha plugins:

grep -rln "session_start" wp-content/plugins wp-content/themes --include=*.php

No hits means these two can’t reach your WordPress site through WordPress. Another application sharing the same server and session directory still could, which is the other half of the serializer bug.

Timezone cache use-after-free

CVE-2026-129496 is a memory bug. If PHP writes a warning to its file-based error log while it starts up, it can keep a pointer to freed memory. A crafted request can then crash a worker, and in demonstrated cases with extra conditions, run native code. The trigger is a startup warning. Examples given in the advisory: an invalid date.timezone value, or a warning caused by session configuration. A server whose PHP starts cleanly doesn’t meet the condition. Check your PHP error log for warnings that appear every time PHP starts, and fix them. That’s worth doing anyway.

PHP-FPM request smuggling

CVE-2026-129289 lets a malformed upload leave unread bytes in a connection that the web server then reuses for the next request. With PHP-FPM, those bytes can be read as a new FastCGI request that the web server never created, carrying settings that make PHP run the attacker’s code. It needs two things: a web server that keeps backend connections open, and an application path that starts reading the request body without finishing it. Configurations named in the advisory:

  • nginx with fastcgi_keep_conn on
  • Apache mod_proxy_fcgi with enablereuse=on
  • HAProxy FastCGI with persistent backend connections
  • LiteSpeed’s LSAPI

Standard nginx and Apache setups that close the connection after each request aren’t affected by the demonstrated attack. LiteSpeed hosts, which run many WordPress sites, are on the list: the advisory says LSAPI shares the faulty cleanup, though it doesn’t use the FastCGI mechanism the demonstrated attack relies on. If your host runs LiteSpeed, confirm that their PHP packages are updated.

The other nine

  • PHAR signature bypass (high): an attacker who can modify an OpenSSL-signed phar archive can downgrade its signature type to a plain hash. This only matters for applications that run signed phar files.
  • PHP-FPM epoll use-after-free: local privilege escalation on the server.
  • PHP-FPM status page XSS: if the FPM status page is reachable, lock it down. It shouldn’t be public anyway.
  • php-cgi out-of-bounds read and write: only with php-cgi and certain web server path mappings. PHP-FPM and Apache’s mod_php aren’t affected.
  • Use-after-free after an interrupted session shutdown, another session bug.
  • Two SOAP bugs: an information leak and a use-after-free on DTD entities.
  • Mixed-case HTTPS:// and FTPS:// URLs could be fetched without encryption.
  • Folded HTTP response headers could cause a denial of service in PHP’s HTTP client.

What to do

1. Confirm the version

You want 8.2.36, 8.3.37, 8.4.28 or 8.5.13 or later. Check again in a few days if your host hasn’t updated yet, and ask them if a week goes by.

2. If you manage PHP yourself, check these settings while you’re there

php -i | grep -E "session.upload_progress.enabled|session.serialize_handler|date.timezone"

Run it with the same PHP your web server uses, or use wp eval 'print_r( ini_get_all( "session", false ) );', because the command line can have its own configuration. If nothing on the server uses session upload progress, turning session.upload_progress.enabled off removes that attack path for good. Set date.timezone to a valid value so PHP starts cleanly. If you use FastCGI connection reuse, make sure the update is in before you rely on it.

3. Know your session users

Run the session_start grep above. Plugins that use PHP sessions are worth knowing about for other reasons too: sessions can break page caching and load balancing.

4. If you share a server, think about neighbors

The serializer bug can cross between applications that share a session directory. Separate sites should have separate session storage (session.save_path), and FPM pools don’t provide that by default.

Where sources disagree

  • CVE-2026-115560’s status. When PHP disclosed it on October 23, it affected even the releases that had just fixed PHP2Shell. Today’s releases are its first fix, not a second attempt. If you treated October’s update as the end of PHP2Shell, this is the rest of it.
  • Severity versus reach. PHP rates four of these critical. Each needs a specific configuration: sessions in use, a startup warning, or connection reuse. On a typical WordPress site with no session plugins and a clean PHP startup, most of the risk drops away. The update is still the fix.
  • Exploitation. None is reported. The advisories are detailed, and the PHP2Shell flaws were attacked within days of disclosure, as covered in PHP2Shell, One Week Later.

The bigger lesson

Both session bugs end the same way: PHP turns data into objects, and a class somewhere in the application does something dangerous when it’s created or destroyed. It’s the same mechanism behind last month’s Gravity Forms object injection. Every library a plugin bundles, Guzzle and Monolog included, adds classes an attacker might use. You can’t remove them all, but you can keep the doors to deserialization shut: fewer plugins that use PHP sessions, a PHP that starts without warnings, and a host that patches quickly.

And it’s a reminder that WordPress security isn’t only WordPress. The server underneath has its own update schedule, and most site owners never see it. Check it today.

Sources