CVE-2026-119977 is a race condition in WordPress core’s upgrade process. NVD says WordPress 4.7 through 7.1.3 uses predictable, web-accessible staging paths during full-package core upgrades, and that lets an unauthenticated attacker execute code on the server during the upgrade window. WordPress fixed it in 7.1.4 on October 28, 2026, and backported the fix to older branches.
CISA added CVE-2026-119977 to its Known Exploited Vulnerabilities (KEV) catalog on November 3, with a federal due date of November 6 and forensic triage required. The flaw is not open on every page request. It sits around the moment a site upgrades, so the update needs a plan: update, confirm the running version, and check whether a site was hit before you patched.
What CVE-2026-119977 is
The WordPress 7.1.4 release notes list “a weakness in the WordPress upgrade process which can lead to remote code execution during the upgrade window,” reported by Umut Bayram. The HelpHub page for 7.1.4 calls it “a race condition during core updates that could lead to remote code execution.” CISA’s KEV entry classifies it as a time-of-check time-of-use (TOCTOU) race condition, CWE-367.
CVE-2026-119977 at a glance
| Product | WordPress core |
|---|---|
| Affected | 4.7 through 7.1.3 (branch ranges below) |
| Fixed | 7.1.4, plus a backport on each older branch |
| Weakness | CWE-367, time-of-check time-of-use (TOCTOU) race condition |
| CVSS 3.1 (CNA, Wordfence) | 8.1 High, AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| Vendor release | October 28, 2026 (WordPress 7.1.4) |
| NVD published | October 31, 2026 |
| CISA KEV added | November 3, 2026, federal due date November 6, 2026 |
| Forensic triage | Required (CISA) |
| Known ransomware use | Unknown (CISA) |
The 8.1 score comes from Wordfence as the CVE Numbering Authority; NVD carries it as a secondary score rather than a NIST assessment. The high attack complexity in the vector fits NVD’s description, since the attack depends on the window while a full-package core upgrade is in progress.
7.1.4 also fixes a batch of stored XSS issues, an information disclosure in unpublished Customizer changesets and a notes permission issue, and updates the bundled root certificates. Those are separate bugs, but they ship in the same update.
Fixed versions by branch
WordPress says the security fixes were backported “to all branches eligible to receive security fixes (currently through 4.7),” and that only the most recent version is actively supported. When the release post went out, the backports were still in progress. NVD’s branch ranges list the first fixed release on each branch, and the WordPress.org version API now lists each of those releases as outdated, not insecure, so they are published.
| Branch | Vulnerable | First fixed |
|---|---|---|
| 7.1 | 7.1.0 – 7.1.3 | 7.1.4 |
| 7.0 | 7.0.0 – 7.0.7 | 7.0.8 |
| 6.9 | 6.9.0 – 6.9.10 | 6.9.11 |
| 6.8 | 6.8.0 – 6.8.11 | 6.8.12 |
| 6.7 | 6.7.0 – 6.7.10 | 6.7.11 |
| 6.6 | 6.6.0 – 6.6.10 | 6.6.11 |
| 6.5 | 6.5.0 – 6.5.13 | 6.5.14 |
| 6.4 | 6.4.0 – 6.4.13 | 6.4.14 |
| 6.3 | 6.3.0 – 6.3.13 | 6.3.14 |
| 6.2 | 6.2.0 – 6.2.14 | 6.2.15 |
| 6.1 | 6.1.0 – 6.1.15 | 6.1.16 |
| 6.0 | 6.0.0 – 6.0.17 | 6.0.18 |
| 5.9 | 5.9.0 – 5.9.19 | 5.9.20 |
| 5.8 | 5.8.0 – 5.8.18 | 5.8.19 |
| 5.7 | 5.7.0 – 5.7.20 | 5.7.21 |
| 5.6 | 5.6.0 – 5.6.22 | 5.6.23 |
| 5.5 | 5.5.0 – 5.5.23 | 5.5.24 |
| 5.4 | 5.4.0 – 5.4.24 | 5.4.25 |
| 5.3 | 5.3.0 – 5.3.26 | 5.3.27 |
| 5.2 | 5.2.0 – 5.2.29 | 5.2.30 |
| 5.1 | 5.1.0 – 5.1.27 | 5.1.28 |
| 5.0 | 5.0.0 – 5.0.30 | 5.0.31 |
| 4.9 | 4.9.0 – 4.9.34 | 4.9.35 |
| 4.8 | 4.8.0 – 4.8.33 | 4.8.34 |
| 4.7 | 4.7.0 – 4.7.38 | 4.7.39 |
A backport closes this CVE on an old branch, but the branch still lacks everything else that only ships in current releases. If a site can move to 7.1.4, move it.
You can check any version against the WordPress.org API, which returns latest, outdated or insecure:
curl -s https://api.wordpress.org/core/stable-check/1.0/ | jq -r '."7.1.3", ."7.1.4"'
Why the upgrade window matters for your patch plan
NVD ties the attack to full-package core upgrades. Updating a vulnerable site to the fixed release is itself a core upgrade, started by the installed version’s upgrader. Neither WordPress nor NVD publishes a workaround for that, so the precautions below are our operational suggestions, not vendor guidance.
Practical options, in rough order of preference:
- Immutable or container deployments: build a new image or release from the official 7.1.4 package (or the fixed backport for your branch) and redeploy. No in-dashboard core upgrade runs on the live site.
- Hosts you manage with WP-CLI: run the update from the shell during a short window where public traffic is blocked at the proxy, and confirm the version straight after.
- Sites that auto-update: WordPress says sites that support automatic background updates start the update automatically. Confirm it actually finished instead of assuming it did.
Patch and verify with WP-CLI
Start with an inventory: every production site, staging copy, replica and container image, with its installed core version. Internet-facing sites go first.
# Installed core version and available updates
wp core version
wp core check-update
# Update to the latest release (7.1.4)
wp core update
# Or stay on the current branch and take its security backport
wp core update --minor
# Confirm the result and check core files against WordPress.org checksums
wp core version
wp core verify-checksums
wp core verify-checksums compares core files with the official checksums for the installed version and reports modified or unexpected files. Run it after the update, from the real webroot the web server serves. A stale build directory or an old release folder can look patched while the live site isn’t.
For containers, check the running instance, not the image tag:
docker exec <wordpress-container> wp core version --allow-root
If the webroot sits on a persistent volume, a new image may not replace the core files already on that volume. Check the version inside the running container and on the volume itself. Our WordPress with Docker Compose guide shows where those files live in a typical setup.
Check for signs of compromise
CISA lists this CVE with forensic triage required, and it publishes no indicators of compromise with the KEV entry. The checks below are general incident-response steps, not CVE-specific IOCs. A clean result does not prove a site is clean.
After you patch each exposed site
- Preserve access, error and deployment logs from before the update where you can, without delaying the update itself.
- Look at web requests around past core-upgrade timestamps for unexpected requests to temporary or staging locations, followed by unexpected PHP execution. Treat this as a hunting lead, not a known indicator.
- Run wp core verify-checksums and investigate any modified or extra core files.
- Search for PHP files where they don't belong, such as the uploads folder, and review recently changed files under wp-content.
- List administrator accounts (wp user list --role=administrator) and remove anything you can't account for.
- Review wp-config.php, active plugins and must-use plugins for changes you didn't make.
- If you find anything suspicious, follow your incident response process: isolate the site, rotate database and admin credentials and salts, and rebuild from a known-good source.
wp user list --role=administrator --fields=ID,user_login,user_registered
find wp-content/uploads -type f -name '*.php'
find wp-content -type f -name '*.php' -mtime -30
If you run sites behind a reverse proxy, as in our Nginx reverse proxy guide, the proxy access logs are a useful record of what hit a site during an upgrade.
What to do now
CVE-2026-119977 is exploited, the fix has been out since October 28, and every branch from 4.7 up has a fixed release. Update each site to 7.1.4, or at least the fixed backport for its branch, and keep the upgrade window short and closed to the public where you can. Then confirm the version on the live webroot, run wp core verify-checksums, and check exposed sites for compromise, because the update does not undo one.