The bug sits in the updater

WordPress downloads a complete package and unpacks the new files into a directory under wp-content/upgrade, then moves them into place. In versions 4.7 through 7.1.3 that directory name is predictable, and the unpacked copy carries the WordPress installer. An unauthenticated attacker who requests the installer while the unpack is in progress can interact with the staged copy and move on to PHP code execution.1

The vector is AV:N/AC:H/PR:N/UI:N, a network attack with high complexity and no account required.1 That complexity figure reflects the width of the window. Wordfence watched the staging directory in a lab and it stayed reachable for seconds, so a single blind request is unlikely to land. The requests came in volume anyway: more than 18,500 in the first 21 hours after Wordfence’s firewall rule went live, aimed at staged setup-config.php paths, with the first match nine minutes after deployment.1

WordPress released 7.1.4 on 28 October as a security release2, and Wordfence counts 22 vulnerabilities in it, this one among them.1

The update runs the old code

For one update, the site installing the fix runs the code that has the bug. The files on disk are the 7.1.3 files, so they download the package, build the staging directory and run the unpack. The new files take over after the swap.

A site that installs 7.1.4 still passes through that window once, and so does a site moving to 6.9.11 or 7.0.8.1 The change that closes it randomizes the staging directory, adds an index guard, and stops unsafe promotion of staged configuration data.1 Those changes take effect on every update that runs after the fixed files are in place.

Waiting does not help here. Watch the update while it runs, and check the version after the files settle.

What the KEV entry adds

CISA listed the CVE in the Known Exploited Vulnerabilities catalog on 3 November, with a due date of 6 November for federal civilian agencies. The required action tells agencies to apply mitigations per vendor instructions and points to BOD 26-04 and to CISA’s forensics triage requirements.3

The ratings disagree, and the disagreement is worth carrying into the ticket. Wordfence, the CNA behind the record, scores it 8.1 High.13 The GitHub advisory announcing the fix rates the issue Low and, on the copy I read, lists no CVE identifier.4 Both describe the same code. Each rater weighed something different: the seconds-wide window, or the unauthenticated path to code execution on a public site. CISA’s listing says something else, that someone used it, and that is different evidence from a base score.

What goes in the relay

Four questions come first, in this order.

Start with the version. Fixed releases run from 4.7.39 to 7.1.4 across 25 branches,1 and on release day WordPress said the backports to older branches were still shipping while only the current version is actively supported.2 A site on an old branch should confirm the matching build exists rather than assume the newest number applies to it.

Then the upgrade directory. I request wp-content/upgrade/ from outside each host and look at the status. The site that returns a directory listing is the one I call first.

The firewall position comes next. Wordfence notes that the exploit requests a staged PHP file directly, without loading WordPress, so a plugin firewall that has not enabled extended protection can miss it, and the Wordfence free tier receives the rule on 27 November.1 A filter that never sees the request cannot block it.

Last, who watches the update finish. Automatic background updates should pull 7.1.4, and Wordfence’s advice is to check the version rather than assume it arrived.1 That check is cheap: wp core version, or Dashboard > Updates on a site without command line access.

The timing line goes with the answers. Give the owner a window, ask when it starts and ends, and follow up the same day if the update fails partway. A failed update is the case I care about most, because the staging copy stays on disk and the site still reports an old version.

Detection, and the fix I would not hand out

The pattern to hunt for is a direct request to an installer file under the upgrade directory while an update is running.1 On a quiet day that path does not exist. A hit there during a change window is expected; a hit outside one is worth pulling apart.

I would not offer a PHP block on the upgrade directory as a mitigation. WordPress writes into that path on purpose, and a rule nobody tested against the updater breaks core updates on the sites that need them. The random path and the index guard ship with 7.1.4, so the version check handles the same risk without a hand-written rule in the way.

What outlasts this CVE

Any web application that stages an update inside the document root has a version of this problem. The version check belongs in the relay. The staging path belongs in the exposure review, next to the question of whether the web server should serve that directory at all.

I would rather answer that once per platform than once per CVE.


  1. Thomas, A. (2026, October 29). WordPress 7.1.4 patches unauthenticated upgrade-window RCE; exploitation attempts detected after release. Wordfence. https://www.wordfence.com/blog/2026/10/wordpress-7-1-4-security-release-rce/ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎

  2. WordPress. (2026, October 28). WordPress 7.1.4. WordPress News. https://wordpress.org/news/2026/10/wordpress-7-1-4/ ↩︎ ↩︎

  3. National Vulnerability Database. (2026, October 31, last modified November 4). CVE-2026-119977 detail. National Institute of Standards and Technology. https://nvd.nist.gov/vuln/detail/CVE-2026-119977 ↩︎ ↩︎

  4. Jorbin, A. (2026, October 29). A race condition during core updates that could lead to remote code execution (GHSA-4w3m-c66w-69mg). GitHub. https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-4w3m-c66w-69mg ↩︎