
On November 3, CISA added CVE-2026-119977 to its Known Exploited Vulnerabilities catalog. Federal civilian agencies have until November 6 to remediate it. That is tomorrow. If you manage WordPress sites for clients, that deadline is not the interesting part. The interesting part is where the flaw lives. It lives in the update process itself, in the few seconds between WordPress unpacking a new version and finishing the install. The tool you trust to keep sites safe is, briefly, the thing that exposes them.
The flaw in plain terms
WordPress core updates come in two shapes. A partial update changes a few files. A full package update replaces the whole core, and that is the shape that matters here. During a full package upgrade, WordPress extracts the new files, installer included, into a folder under wp-content/upgrade/. The folder name is predictable. The staged copy contains wp-admin/setup-config.php, the WordPress installer, and on many servers that folder is reachable from the web without logging in.
An unauthenticated attacker who requests the staged installer at the right moment can move from reading files to running code with web server privileges. The class of bug is CWE-367, a time of check to time of use race. The window lasts seconds, and it recurs on every full package update, including automatic ones. That is the part worth sitting with. This is not a flaw in a plugin nobody maintains, or a theme a client installed in 2019. It is in the core updater, the routine that runs on millions of sites, and the exposure repeats every time a site updates.
The flaw was reported by Umut Bayram of Picus Security, and WordPress fixed it in 7.1.4, released October 28, 2026. The release post describes it plainly as a weakness in the upgrade process that can lead to remote code execution during the upgrade window.
Who is affected, and what the fix does
Every WordPress release from 4.7.0 through 7.1.3 is affected. The fix landed in 7.1.4, and WordPress backported it to every branch back to 4.7, from 7.0.8 down to 4.7.39. Versions 4.6 and earlier get no fix at all. If you still have a client site on one of those, there is no patch coming. The only honest plan is a migration.
The fix itself does three things. It randomises the staging folder name with a 16 character suffix, so the path is no longer guessable. It adds an index guard to the staging folder. And it stops promoting a staged wp-config.php into place. None of this is exotic. It is the kind of boring hardening that should have been there all along, and that is exactly why it is worth noting. The vulnerability was not a clever bypass. It was a predictable path with no guard on it.
Two scores for the same flaw
Here is a disagreement worth one honest line. Wordfence, which assigned the CVE, rates it CVSS 3.1 8.1 High, with the vector AV:N/AC:H/PR:N/UI:N. WordPress's own advisory, GHSA-4w3m-c66w-69mg, rates the same race Low and carries no CVSS score. The two sides are not really arguing about the same thing. Wordfence scores the worst case, an unauthenticated attacker reaching code execution. WordPress weighs the narrow window and the high attack complexity, and lands on Low.
For anyone managing client sites, the argument matters less than the KEV listing. CISA does not add a vulnerability to that catalog on theory. The listing is based on evidence of active exploitation. Whatever the score, attackers are already trying this one in the wild, and the federal due date of November 6 is the calendar telling you how seriously to take it.
What the traffic actually shows
Wordfence put out a firewall rule at 20:30 UTC on October 28, about three hours after the release announcement. The first matching request arrived nine minutes later. In the first 21 hours after the rule went out, Wordfence logged more than 18,500 requests aimed at staged installer paths. Later counts run higher. The Hacker News, citing Wordfence, reported 62,969 blocked attempts in a 24 hour period.
Read those numbers for what they are. They are attempts and probing, not confirmed compromises. No source reviewed so far has reported a confirmed site takeover tied to this flaw. Two of the largest sources kept polling small groups of sites for about 14 and a half hours, which Wordfence reads as attackers waiting for a target to start updating rather than spraying the whole internet. That pattern is the tell. The attackers are not looking for sites that forgot to patch. They are watching for sites in the act of patching, because that is when the window opens.
The trap: the update to 7.1.4 is still exposed
This is the part that catches people who did everything right. Updating to 7.1.4 itself still runs through the old unpacking code, because the fix only takes effect once the new code is in place. The update that closes the flaw is itself exposed to it. That does not mean you should delay updating. It means you should not treat the update as the whole job. Run it, then check the work.
If you manage WordPress sites for clients, here is the short list for this week.
- Confirm the fixed build per branch under Dashboard, then Updates, rather than assuming auto update ran. The fixed line is 7.1.4, with backports down to 4.7.39. Check the number on each site.
- Before any manual update, block web access to
wp-content/upgrade/at the server. A location block in Nginx or an.htaccessdeny rule closes the path the race depends on, and it costs nothing to leave in place. - Check access logs from October 28 forward for PHP requests under
wp-content/upgrade/. Any hit on a stagedsetup-config.phppath is worth a closer look. - While you are in there, look for unfamiliar admin accounts and unexpected plugins or files. If a staged installer was ever reached, the evidence will be in the user list and the file tree, not in a dashboard banner.
- For sites on 4.6 or earlier, stop planning a patch and start planning the migration. There is no fixed release for those branches.
The durable idea underneath this one is simple, and it applies well past WordPress. An update is a change, and a change is a moment when the system is briefly in a state nobody designed for. Most of the time that state is harmless. Sometimes it is a web accessible folder with an installer in it. The fix for that is not a better update button. It is checking what the update actually did, and closing the paths it opened along the way.
Sources
- WordPress 7.1.4 (WordPress.org, October 28, 2026)
- CISA Adds One Known Exploited Vulnerability to Catalog (CISA, November 3, 2026)
- WordPress 7.1.4 Patches Unauthenticated Upgrade-Window RCE; Exploitation Attempts Detected After Release (Wordfence, October 29, 2026)
- CVE-2026-119977 (CVE.org, published October 31, 2026)



