What is WordPress Core?
WordPress Core is the PHP content management system behind a large share of the public web, put at roughly 39.5% of all websites by W3Techs. Core ships an in-place updater: when a new release lands, the site downloads the full release ZIP, unpacks it into a working directory under wp-content/upgrade/, copies the new files over the live installation, and deletes the staging copy. That updater runs unattended on most installations, including via WP-Cron, which means the vulnerable moment arrives on its own schedule rather than when an administrator chooses. Any flaw in it is reachable on an enormous number of hosts without an attacker needing a single credential.
Overview
CVE-2026-119977 is a time-of-check time-of-use race condition in that updater. Affected versions unpack a full-package core update into a staging directory whose name is derived from the package filename, for example wp-content/upgrade/wordpress-7.1.4/. That directory is usually served by the web server and PHP will execute files inside it. The unpacked tree includes wp-admin/setup-config.php, the first-run installer. Its safety guard only refuses to run when a wp-config.php is present, and release packages ship only wp-config-sample.php, so the guard never fires. For the few seconds between unpacking and cleanup, an unauthenticated attacker who requests that path reaches a live installer running as the web server user.
Wordfence, the CNA for this record, scores it 8.1 HIGH (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), with attack complexity High because of the race. WordPress rates the same defect Low in its own advisory. The gap is real and worth noting: exploitation is unauthenticated and fully remote, but only during an update. Attackers resolved the complexity problem by polling continuously, and CISA added the CVE to the KEV catalog on 2026-11-03 with an unusually short three-day deadline of 2026-11-06.
Two secondary details make the window worse than it sounds. Before 7.1.4, cleanup deleted the index.php that suppresses directory listing, so on servers with listing enabled the staging folder name could simply be read. And the staged setup-config.php bootstraps WordPress from its own copy of core, so a WordPress firewall plugin loaded by the live installation never sees these requests at all.
Affected Versions
| Product | Vulnerable | Fixed |
|---|---|---|
| WordPress Core (current branch) | 4.7.0 through 7.1.3 | 7.1.4 |
| WordPress Core 7.0 | 7.0.7 and prior | 7.0.8 |
| WordPress Core 6.9 | 6.9.10 and prior | 6.9.11 |
| WordPress Core 6.8 | 6.8.11 and prior | 6.8.12 |
| WordPress Core 6.0 - 6.7 | all prior | 6.0.18, 6.1.16, 6.2.15, 6.3.14, 6.4.14, 6.5.14, 6.6.11, 6.7.11 |
| WordPress Core 4.7 - 5.9 | all prior | backports down to 4.7.39 |
| WordPress Core 4.6 and earlier | vulnerable | no fix; migrate to a supported branch |
Technical Details
The weakness class is CWE-367: the updater checks a condition and then acts on it, and an attacker can change what matters in between. In plain terms, core writes a complete, executable copy of WordPress to a guessable web-reachable path, then validates and cleans up afterwards. Everything an attacker needs is public knowledge: the directory naming scheme, the release version string, and the installer path inside the package.
Exploitation needs no account and no user interaction, but it does need four conditions at once: a full-package core update in progress, web and PHP access to wp-content/upgrade/, a predictable or discoverable staging path, and a request landing before deletion. Observed attempts are not single well-formed requests but sustained polling of one path for hours, waiting for a site to update.
WordPress 7.1.4 closes all three legs. The staging directory name now has 16 random characters appended, index.php is recreated and no longer deleted, and update-core.php no longer copies wp-config.php out of the working directory.
Discovery
The WordPress 7.1.4 release post credits Umut Bayram with the upgrade-process weakness, reported through coordinated disclosure. One secondary write-up gives the affiliation as Picus Security; that attribution is not in the vendor post and could not be independently confirmed. Wordfence published the CVE record on 2026-10-31 and supplied the technical analysis of the staged installer path. WordPress's own advisory describes the issue only as "a weakness in the WordPress upgrade process which can lead to remote code execution during the upgrade window" and gives no mechanism.
Exploitation Context
Defiant, Wordfence's parent, reported attackers probing for the staged installer within hours of the 7.1.4 announcement. Wordfence deployed a firewall rule at 20:30 UTC on 2026-10-28, roughly three hours after release, and recorded the first matching request nine minutes later. In the following 21 hours it logged more than 18,500 requests targeting staged setup-config.php paths; one secondary source cites a higher figure of 62,969 blocked attempts in the 24 hours to 2026-10-30. These are blocked attempts, not compromises.
Traffic shape divides into two groups. Two large sources polled the same small set of sites for roughly 14.5 hours, consistent with waiting for a specific target to update. Others cycled through folder and version-name variations, consistent with untargeted scanning. No threat actor attribution has been published, no public proof of concept was found as of 2026-11-02, and neither CISA, WordPress, nor Wordfence has described a specific compromised site. CISA does not publish the evidence behind a KEV listing, so the basis for the 2026-11-03 addition is not public. No chaining with other CVEs has been reported.
Remediation
- Update to 7.1.4, or to the backport for your branch: 7.0.8, 6.9.11, 6.8.12, 6.7.11, 6.6.11, 6.5.14, 6.4.14, 6.3.14, 6.2.15, 6.1.16, 6.0.18, down to 4.7.39. Sites on 4.6 or earlier get no fix and must move to a supported branch.
- Before updating an unpatched site, block web access to
/wp-content/upgrade/at the web server, in.htaccess, or at the CDN or WAF, and confirm it returns 403 and does not list the directory. The update that installs the fix still runs the old updater, so the last unprotected window is the one that installs the patch. - Verify sites deployed by Composer, git, container image, or with
DISALLOW_FILE_MODSenabled. They never run the built-in updater, but they still need the fixed code. - Review web and WAF logs for any PHP request under
wp-content/upgrade/, prioritising HTTP 200 responses. Treat a 200 on a POST to a stagedsetup-config.phpas probable compromise. Narrow the search by finding each site's update time from the mtime ofwp-includes/version.phpor fromdo-core-upgraderequests, then review five minutes before to ten minutes after. - Check for post-compromise indicators: unexpected administrator accounts, new or altered plugins and themes around the update time, PHP files in
uploads,upgrade, ormu-plugins, leftover content inwp-content/upgrade/beyondindex.php, and changes towp-config.phpor.htaccess. Runwp core verify-checksums. - If compromised, take the site offline, preserve files, database, and logs, rebuild from a clean fixed release, restore content from a pre-update backup, and rotate database credentials, salts and keys, administrator passwords, and hosting and third-party API credentials.
- Federal civilian agencies must remediate by 2026-11-06 under BOD 26-04 and complete the directive's forensic triage requirements.
Key Details
| Property | Value |
|---|---|
| CVE ID | CVE-2026-119977 |
| Vendor / Product | WordPress - WordPress Core |
| NVD Published | 2026-10-31 |
| NVD Last Modified | 2026-11-03 |
| CVSS 3.1 Score | 8.1 |
| CVSS 3.1 Vector | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| Severity | HIGH |
| CWE | CWE-367 find similar ↗ |
| CISA KEV Added | 2026-11-03 |
| CISA KEV Deadline | 2026-11-06 |
| Known Ransomware Use | No |
CVSS 3.1 Breakdown
Required Action
Timeline
| Date | Event |
|---|---|
| 2026-10-28 | WordPress 7.1.4 released, fixing the upgrade-window weakness reported by Umut Bayram |
| 2026-10-28 | Wordfence ships a firewall rule at 20:30 UTC; the first matching request arrives nine minutes later |
| 2026-10-31 | CVE-2026-119977 published by Wordfence as CNA, scored 8.1 HIGH |
| 2026-11-03 | Added to CISA Known Exploited Vulnerabilities catalog |
| 2026-11-06 | CISA BOD 26-04 remediation deadline |
References
| Resource | Type |
|---|---|
| NVD - CVE-2026-119977 | Vulnerability Database |
| CISA KEV Catalog Entry | US Government |
| WordPress 7.1.4 Security Release | Vendor Advisory |
| Wordfence - WordPress Core 4.7.0 - 7.1.3 Unauthenticated Upgrade-Window Staged-Installer Remote Code Execution | Security Research |
| CISA Alert - CISA Adds One Known Exploited Vulnerability to Catalog | US Government |
| SecurityWeek - Fresh WordPress Vulnerability in Attackers' Crosshairs | News |
| Ostorlab - WordPress Core Upgrade-Window RCE, Fixed in 7.1.4 | Security Research |
| ThreatDefence - WordPress 7.1.4 Upgrade-Window RCE: Hunting CVE-2026-119977 | Security Research |