WordPress 7.1.5 patches race-condition RCE after CISA deadline
WordPress 7.1.5 fixes a race-condition RCE (CVE‑2026‑119977) that CISA flagged for federal agencies, plus privilege escalation and XSS issues. The patch follows earlier emergency fixes and a November deadline for agencies.
WordPress released version 7.1.5 on November 18, 2026, to patch a race‑condition bug in its upgrade process (CVE‑2026‑119977) that CISA added to its Known Exploited Vulnerabilities catalog on November 3, 2026. The patch follows an earlier emergency update in October that stopped the same race condition from being abused, and it comes amid a series of recent WordPress security releases that have been fixing both RCE paths in quick succession.
How the upgrade race lets attackers run code
The race condition lives in how WordPress handles temporary files when it installs or updates itself. A malicious actor can craft a request that hits the upgrade directory while WordPress is creating and then deleting temporary files, essentially catching the server in the middle of a rename operation. That timing window lets them execute arbitrary PHP code without logging in, because the file system sees a legitimate temporary file just long enough for the web server to run it.
Patch rollout and what’s next
Federal civilian agencies had until November 6, 2026, to upgrade to WordPress 7.1.4 to address CVE‑2026‑119977, per CISA’s directive. The new 7.1.5 release plugs the race condition more broadly and also fixes a JSON media‑type regex that can broaden matching, a privilege escalation in multisite Customizer previews, and a reflected XSS in the legacy media popup. These extras increase the risk surface for sites that linger on older versions.
WordPress has been churning out security fixes at a fast clip. Version 7.1.4, released October 28, 2026, included the same race‑condition patch plus 22 other fixes, while 7.1.2, released September 22, 2026, addressed CVE‑2026‑87902. The pattern suggests the project is treating core security as a continuous process rather than a periodic event.
Timeline
| Date | Event |
|---|---|
| September 22, 2026 | WordPress 7.1.2 patches CVE‑2026‑87902 (unauthenticated RCE) |
| October 28, 2026 | WordPress 7.1.4 patches CVE‑2026‑119977 race condition and adds 22 fixes |
| November 3, 2026 | CISA adds CVE‑2026‑119977 to its Known Exploited Vulnerabilities list |
| November 6, 2026 | Federal deadline to upgrade to 7.1.4 (for CISA‑mandated agencies) |
| November 18, 2026 | WordPress 7.1.5 closes CVE‑2026‑119977 and other high‑severity issues |
Outlook
The immediate priority is to get all supported installations to 7.1.5 and keep the wp‑content/upgrade/ directory off the web. Until then, any scheduled upgrade is a potential attack surface, and the combination of race‑condition RCE and other flaws makes it easy for opportunistic scanners to find and exploit vulnerable sites. If exploitation continues at the same pace, we may see another focused release before the next major version lands.