(647) 243-4688

PHP published advisories for several critical vulnerabilities on November 19, 2026, with fixed PHP releases published on November 18 and 19. WordPress site owners should update PHP as soon as possible.

  • CVE-2026-129289 is the most directly relevant issue for WordPress. On an affected PHP-FPM server, an unauthenticated attacker may be able to make PHP run a request that never passed through the web server’s normal checks.
  • Not every WordPress site is exposed. The demonstrated attack requires a vulnerable PHP version and a web server that reuses its private connections to PHP-FPM. Standard NGINX configurations do not enable that reuse by default.
  • The Wordfence Threat Response team confirmed unauthenticated code execution in an isolated WordPress lab. The same test did not run code after PHP was updated or after reuse of the web-server-to-PHP connection was disabled.
  • Fixed releases for the affected supported branches are 8.2.36, 8.3.37, 8.4.28, and 8.5.13. Hosting vendors may also provide backported fixes under different package version numbers.

On November 19, 2026, PHP published CVE-2026-129289, a critical PHP-FPM vulnerability with a CVSS v4.0 score of 9.2 out of 10. Successful exploitation can let an attacker run PHP code with the permissions of the website’s PHP process.

This is a vulnerability in PHP, not WordPress Core, a plugin, or a theme. However, normal WordPress REST API processing provides one of the application behaviors needed by the attack. Updating WordPress will not update PHP. On managed hosting, follow guidance from your host. On a self-managed server, install the PHP fix and restart or redeploy the affected service.

How CVE-2026-129289 Works

A web server such as NGINX normally checks an incoming request and then passes it to PHP-FPM over a private connection. CVE-2026-129289 can cause PHP to leave part of a request unread. If the web server keeps that private connection open and reuses it, PHP may treat the leftover bytes as a new request.

That second request did not go through the web server’s normal routing or access checks. According to PHP’s advisory, an attacker who knows the path to an existing PHP file can use it to run PHP code without logging in. The attack does not depend on corrupting memory, predicting a memory address, or winning a timing race.

The required connection reuse is not NGINX’s default. NGINX documents fastcgi_keep_conn off as the default. However, this is a real production setting: WordOps, a server-management tool for WordPress, currently enables fastcgi_keep_conn on and defines cached PHP-FPM connections in its NGINX templates. PHP’s advisory also identifies Apache mod_proxy_fcgi with enablereuse=on as an affected configuration. Our lab testing covered NGINX, not Apache.

Why WordPress Is Relevant

PHP’s advisory says the application must open php://input, which represents the incoming request body, while affected bytes remain unread. WordPress REST requests normally call WP_REST_Server::serve_request(), which uses WP_REST_Server::get_raw_data() to read php://input. In our tested path, a specially formed request body made PHP’s parser stop early, and the PHP bug left crafted bytes on the reused private connection when WordPress reached this code.

This REST request behavior is part of stock WordPress Core. The demonstrated route did not require a vulnerable plugin or theme, a WordPress account, an existing session, or attacker-created content. The server still had to be running a vulnerable PHP-FPM release and reusing the private connection between the web server and PHP.

What Wordfence Testing Found

The Wordfence Threat Response team reproduced unauthenticated PHP code execution through a stock WordPress 7.1.5 REST request in an isolated lab. The vulnerable target used PHP 8.2.35 behind NGINX with PHP-FPM connection reuse enabled. The same request did not run code on an otherwise matched PHP 8.2.36 target or when connection reuse was disabled.

As of November 20, 2026, CVE-2026-129289 is not listed in CISA’s Known Exploited Vulnerabilities catalog. Public technical details are available, so site owners should not wait for evidence of exploitation before updating.

Affected and Fixed PHP Versions

Affected PHP versions First fixed PHP release
PHP 5.6.0 through 8.1.x (unsupported branches) No fixed release; move to a supported branch
PHP 8.2.0 through 8.2.35 8.2.36
PHP 8.3.0 through 8.3.36 8.3.37
PHP 8.4.0 through 8.4.27 8.4.28
PHP 8.5.0 through 8.5.12 8.5.13

PHP says the vulnerable code dates to PHP 5.6.0, so unsupported PHP 5.6 through 8.1 releases may also be affected. Sites on unsupported branches should move to a supported, fixed release.

Linux distributions and hosting vendors may backport the fix without changing the first three version numbers. If your host manages PHP, check its security notices, status page, dashboard, or customer communications for guidance. If you manage the server, check the complete package revision and the vendor’s security notice. Also make sure you are checking the PHP-FPM version that serves the website; the command-line PHP version can be different. WordPress Site Health can report the web process’s PHP version, but it cannot confirm a vendor backport or whether every affected PHP process was restarted.

What About the Other Critical PHP Vulnerabilities?

PHP disclosed six other critical vulnerabilities as part of the same November security-release cycle. They are important reasons to update, but their documented attacks require more specific server settings, application behavior, or additional steps on an ordinary WordPress site:

Issue Main extra condition What it means for WordPress sites
CVE-2026-129496
Timezone cache memory error
A particular startup diagnostic written through PHP’s file-based error log, followed by an early diagnostic in a fresh PHP worker. Important server-level concern. Remote PHP-FPM worker crashes were demonstrated. The published code-execution tests required the attacker to know process memory addresses and depended on additional server settings, so this is not a confirmed general WordPress takeover path.
CVE-2026-126714
Partly overwritten session files
PHP file-based sessions, attacker influence over session data, an interrupted write, a later read, and suitable application code. Low risk from WordPress Core alone. WordPress Core does not use native PHP sessions, but a plugin, theme, custom code, or another application can add them.
CVE-2026-115560
Session format mismatch
PHP’s upload-progress feature writes a session using one format, and a later or concurrent operation reads the same session ID and storage using another format. Narrow, but relevant when applications share PHP session storage. Stock WordPress does not normally create the required PHP session, but shared session storage across applications can.
CVE-2026-129481
Interrupted session shutdown
Application code must fail during session cleanup, followed by another request reaching the same PHP process. Application-dependent. PHP confirmed a memory error and crashes, but did not demonstrate code execution through this specific path.
CVE-2026-129474 and CVE-2026-129182
Fatal-error backtrace memory errors
PHP 8.5 plus particular error-reporting or server settings and application behavior. Lower priority for a general WordPress warning. The demonstrated CVE-2026-129474 attack is blocked by PHP’s standard php.ini-production configuration; code execution was not shown for the CVE-2026-129182 path.

These differences help explain likely exposure; they are not a reason to leave PHP unpatched. The fixed release for each PHP branch addresses every listed issue that affects that branch.

What WordPress Site Owners Should Do

  1. Managed or shared hosting: Check your host’s security notices, status page, dashboard, or customer communications for guidance about the November 19 PHP security updates. Follow any instructions your host provides.
  2. Self-managed servers: Install PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13, a later supported release, or your vendor’s fixed package. Restart PHP-FPM and any web server processes that may retain private connections to it.
  3. Containers: Rebuild and redeploy from a fixed PHP base image. Restarting an old container does not replace the vulnerable files inside it.
  4. If an update is not immediately available: Disable PHP-FPM connection reuse at the web server until the update can be installed. This blocks the demonstrated CVE-2026-129289 path, but it does not fix the other PHP vulnerabilities.
  5. Test after updating: Confirm that the site, REST API, scheduled tasks, and important plugin functions still work, and verify the PHP-FPM version actually serving the site.

Updating WordPress, plugins, themes, or Wordfence does not update PHP. Keep those components current as well. On managed hosting, follow guidance from your host. On a self-managed system, install the fixed package or image supplied by the operating-system or platform vendor.

Conclusion

CVE-2026-129289 does not affect every WordPress site, but it creates a credible unauthenticated threat on WordPress servers that run a vulnerable PHP-FPM version and reuse web-server-to-PHP connections. Stock WordPress provides the relevant REST request behavior, and our lab testing confirmed code execution when the server conditions matched PHP’s advisory.

Do not delay the update while determining whether the exact server configuration is exposed. Install the fixed PHP release or vendor package, restart or redeploy the affected services, and verify the PHP-FPM version used by the website.

Sources

Sign up for the Wordfence mailing list to receive important WordPress security news and vulnerability reports as soon as they are published.

The post CVE-2026-129289 and Other Critical PHP Vulnerabilities: What WordPress Site Owners Need to Know appeared first on Wordfence.