Skip to content
Blog

WordPress · WordPress Core · race condition

WordPress Core CVE-2026-119977 in CISA KEV: Code Execution During the Upgrade Window

CVE-2026-119977 (8.1): race condition in WordPress core upgrades up to version 7.1.3, exploitable without an account. Added to CISA KEV, due November 6.

5 min readCVE-2026-119977

On November 3, 2026, CISA added CVE-2026-119977 to its KEV catalog with a due date of November 6: three days. The flaw sits in WordPress core, versions 4.7 through 7.1.3, and lets an unauthenticated attacker execute code on the server.

What makes it unusual is when it can be exploited: only while a core upgrade is running. In other words, the most basic security habit is what opens the window.

This is the second WordPress core entry in KEV in two months, after CVE-2026-87902 in late September.


The vulnerability

FieldValue
CVECVE-2026-119977
CVSS 3.1 (Wordfence, CNA)8.1 (HIGH) — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
TypeTOCTOU race condition (CWE-367)
Authenticationnone
Affected versions (NVD)4.7 through 7.1.3
NVD publication2026-10-31
NVD statusUndergoing Analysis (no NVD score of its own, no CPE configuration)
Added to CISA KEV2026-11-03
CISA due date2026-11-06
Ransomwareunknown per CISA

NVD description:

WordPress Core is vulnerable to Remote Code Execution in versions 4.7 through 7.1.3. This is due to predictable, web-accessible staging paths used during full-package core upgrades.


How it works

During a full-package core upgrade, WordPress downloads the new release archive, unpacks it into a staging directory, then copies the files into place. According to NVD, that staging directory has two problems:

  • its path is predictable;
  • it is reachable over the web.

Until the upgrade finishes, the unpacked files can be requested over plain HTTP at an address the attacker can guess. That is the textbook definition of a TOCTOU (time-of-check, time-of-use) bug: between the moment files are dropped and the moment they are moved or deleted, someone else gets to use them.

The NVD references point to class-core-upgrader.php, class-wp-upgrader.php and update-core.php, which drive the process, but also to wp-admin/setup-config.php, the WordPress installer, and the Wordfence advisory talks about a "staged installer". A likely reading, and it is only an inference: the unpacked archive contains an installer that, when called from its temporary location, does not behave as it would on an already-installed site. NVD does not go further into the exploitation path.

Why "high complexity" is not reassuring

The vector says AC:H: you have to hit the upgrade window, which lasts a few seconds. But:

  • automatic core updates run unattended on millions of sites, usually shortly after a release ships;
  • an attacker does not need to guess the timing. They can poll the predictable path across a large number of sites and wait for one to answer.

A KEV listing means CISA has evidence of exploitation. It also requires forensic triage (BOD 26-04) on top of patching.


Affected versions and fix

Affected range (NVD)First version out of range
4.7 → 7.1.37.1.4

The WordPress 7.1.4 release notes, referenced by both CISA and NVD, are the fix reference. NVD has not published a CPE configuration yet, so the bound comes from the description ("through 7.1.3"). If you are on an older branch, check wordpress.org for a backported fix for that branch; otherwise, the answer is moving to 7.1.4.

Check a site's version:

wp core version

The upgrade paradox

The fix ships as an upgrade, and the upgrade is the exploitation window. Moving to 7.1.4 is driven by the upgrade code of the currently installed, vulnerable version. That is no reason to wait: it is the last window, and it lasts seconds. It is, however, a reason to run that upgrade under controlled conditions (see below) rather than letting it fire at a random moment.


Detection

  • Web server access logs: requests to WordPress upgrade directories (usually under wp-content/upgrade/) or to setup-config.php, especially around core update times
  • Bursts of 404s on paths under wp-content/upgrade/: a sign of someone polling
  • Recent PHP files in wp-content/, wp-content/uploads/ or the web root that do not match a plugin update
  • Recently created admin accounts: wp user list --role=administrator
  • Changes to wp-config.php around an upgrade date
wp core verify-checksums

That command compares core files against the official checksums. It does not see files added under wp-content/, which need a separate look.


Mitigation

1. Move to WordPress 7.1.4 before November 6

Across a fleet, prefer a controlled upgrade over waiting for the automatic one.

2. Block web access to staging directories during upgrades

A precaution inferred from the mechanism NVD describes: a web server (nginx, Apache) or WAF rule denying all HTTP requests to wp-content/upgrade/ closes the window, since the upgrade runs server-side and never needs those files to be served.

3. Upgrade in maintenance mode or off the public internet

For sensitive sites, run the upgrade while access is restricted (IP allowlist, maintenance page at the web server level).

4. If in doubt

Rotate the secrets in wp-config.php (database credentials, keys and salts), review admin accounts and scheduled tasks, and diff files against a pre-incident backup.


Why continuous monitoring of your WordPress fleet matters

An 8.1 with high attack complexity and no NVD score of its own lands in KEV with a three-day deadline. Across a fleet of sites, the useful question is which ones are still running something between 4.7 and 7.1.3, and knowing that on the day of the listing.

With cveo.tech, track your WordPress sites with their exact version and get an alert as soon as a CVE affecting them is added to the CISA KEV catalog.

Running WordPress sites? Know which CVEs hit your version.

Add the product and its version: cveo.tech lists the CVEs that affect it right away, then alerts you by email when a new one affects it — including before NVD has finished its analysis. Free, an account is all it takes.

Every Monday

The week's critical CVEs, in your inbox

One email a week: the CVSS ≥ 9 vulnerabilities published in the last seven days, plus our latest analyses. Nothing else.

Double opt-in by email. Unsubscribe in one click, any time.