WordPress Core update RCE (CVE-2026-119977): fix and log checks
Until WordPress 7.1.4, a full-package Core update left its extracted installer reachable under wp-content/upgrade/ for a few seconds. Attackers poll for that window: Wordfence counted more than 240,000 blocked requests by 5 November, and the flaw is in CISA’s Known Exploited Vulnerabilities catalog. The fix is 7.1.4 or the backport for your branch, plus a web-server rule that denies the folder, put in before the update on any site still to run it.
Prepared by G. Schad, WordPress and Linux security specialist
This page collects the coverage of CVE-2026-119977 from the weekly briefings of 2 and 9 November 2026, oldest first. Each section is dated.
Affected
WordPress Core 4.7 through 7.1.3, during a full-package update
Fixed in
7.1.4 (28 October 2026) and same-day backports down to 4.7.39
Exploitation
In CISA’s KEV; over 240,000 blocked attempts per Wordfence by 5 November, no confirmed compromise reported
Do also
Deny wp-content/upgrade/ at the web server; search the access logs for PHP requests under it
2 November · WordPress Core · CVE-2026-119977
WordPress 7.1.4: the update process left the installer on the web for a few seconds
WordPress 7.1.4 was released on 28 October as a security release with 22 fixes, most of them stored cross-site scripting reachable by Contributor or higher accounts, plus an information disclosure of unpublished Customizer changes, a permissions bug in post notes, and an update to the bundled root certificates. The one that matters to this briefing was reported by Umut Bayram and described by WordPress as a race condition during core updates that could lead to remote code execution. It affects every version from 4.7 to 7.1.3, which is to say every WordPress that has updated itself in the last decade. Wordfence assigned CVE-2026-119977 and scored it 8.1; Patchstack’s database entry carries a 9 with a Low priority and the note that exploitation is impractical. CISA added it to the Known Exploited Vulnerabilities catalog on 3 November with a 6 November deadline for federal agencies, which is a three-day window and a signal of how it reads the evidence.
The mechanism, from Patchstack’s reading of the code, is this. When WordPress installs or updates itself from a full package, it extracts the archive into a working folder under wp-content/upgrade/, a directory the web server serves. Before 7.1.4, the folder name came from the package name, so for an administrator-uploaded or standard update it was predictable. The cleanup routine then deleted everything in wp-content/upgrade/, including the index.php that stops directory listing. The extracted copy is a complete WordPress, and it contains wp-admin/setup-config.php, the installer that runs without the site’s configuration. An attacker who requests that file while the extraction exists can run the installer against a database they control, and from there execute code. The window lasts as long as the extraction and copy take, which is seconds on fast storage and longer on NFS, saturated disks or staged deployments. It recurs on every update, including unattended ones, and it needs no account.
The paths the attackers request look like this, with the directory name varying by package:
7.1.4 adds three defences: sixteen random characters appended to the extraction folder name, an index.php that is recreated and no longer deleted, and wp-config.php added to the list of files never copied out of the working directory, a change Patchstack found in update-core.php and the release post does not mention. The backports shipped the same day for every branch WordPress still patches: 7.0.8, 6.9.11, 6.8.12, 6.7.11, 6.6.11, 6.5.14, 6.4.14 and so on down to 4.7.39. WordPress’s own documentation lists which of the 22 issues reach each branch; 7.0 and 6.9 get all 22, 6.8 and 6.7 get 20, 6.6 gets 19. The 28 October announcement said the backports were in progress and would ship as ready, so a site on an older branch should be checked rather than assumed. 4.6 and earlier get nothing.
The durable fix is a web-server rule, so the folder is never served whatever WordPress does inside it. On Apache or LiteSpeed it is a two-line file in the folder itself; on nginx it is a location block in the site’s server block, ahead of the PHP location:
wp-content/upgrade/.htaccessNew file+2 linesShow the changeHide
Apache or LiteSpeed
1+Added: # Nothing under wp-content/upgrade/ is ever requested over HTTP.2+Added: Require all denied
WordPress keeps index.php in this folder from 7.1.4, and older versions can delete other files in it during cleanup, so on those the vhost-level rule is the one that lasts. A request for anything under the folder now gets 403.
nginx server block for the siteAdd+3 linesShow the changeHide
The ^~ prefix makes nginx stop at this block, so the PHP location further down never sees the request. Reload nginx after testing the configuration with nginx -t.
Wordfence published a firewall rule at 20:30 UTC on 28 October and saw the first matching request nine minutes later. In the first 21 hours it counted more than 18,500 requests for staged setup-config.php paths. Those are attempts seen by one vendor’s firewall, not compromises; Wordfence has not reported a successful one, and neither has anyone else as of this briefing. Treat the number as proof that the path is being polled at scale, and your own logs as the only evidence about your own sites.
Figure 1 · At a glance
The installer is reachable for seconds during an update. Deny the folder, then update.
Question
Answer
What is exposed
The staged installer under wp-content/upgrade/, during a full-package update
Fixed in
WordPress 7.1.4 and backports down to 4.7.39, 28 October 2026
Attempts seen
Over 240,000 blocked per Wordfence; peak above 74,000 on 30 October
Durable fix
A web-server rule denying wp-content/upgrade/, in place before the update runs
Look for
Requests for PHP under that folder that got anything other than 403 or 404
The points that decide what to do about the WordPress Core update-window flaw CVE-2026-119977, as stated in the sections below.
If a site updated between 28 October and the fix, read these before you call it clean
For every site that ran a Core update while wp-content/upgrade/ was web-reachable, which until this week was all of them. The order is preserve, then search, then verify, then audit. Nothing here changes the site.
01
Search the access logs for the staged installer
On cPanel the per-domain logs are in domlogs; elsewhere use the vhost access log. Any hit is worth a ticket, a 200 is an incident:
A 403 after this week’s deny rule is the rule working. A 404 from before it means the attacker missed the window. A 200 or 302 means the installer answered.
02
Look for what the extraction left behind
Between updates the folder holds only index.php. Anything else, and above all a wp-config.php or any PHP file that is not index.php, is evidence:
Check the live wp-config.php against a known-good copy as well, since the pre-7.1.4 copy routine could promote one.
03
Verify the Core files
Confirm the version and that the Core files match the release checksums, with plugins and themes skipped so nothing loaded can interfere:
WP-CLI
$ wp core version --skip-plugins--skip-themes$ wp core verify-checksums --skip-plugins--skip-themes
A checksum failure on a file the release touched is expected after a partial update; a failure on a file it did not touch, or an extra file, is not.
04
Audit who and what arrived after the update
Administrators, application passwords, plugins, must-use plugins and cron events created in the hours after an update are the shapes a successful run would take:
shell
$ wp user list --role=administrator--fields=ID,user_login,user_email,user_registered--skip-plugins--skip-themes$ wp user application-password list "$(wp user list --role=administrator --field=ID --skip-plugins --skip-themes | head -1)"--skip-plugins--skip-themes$ wp plugin list --fields=name,status,version,update--skip-plugins--skip-themes$ wp cron event list --fields=hook,next_run_relative,recurrence--skip-plugins--skip-themes$ ls-la--time-style=long-iso wp-content/mu-plugins wp-content/plugins |sort-k6,7
Then the process table and outbound connections for the account during the same window, which on shared hosting is where the question becomes a server question.
The update-window RCE: 240,000 attempts, ten addresses and one last vulnerable update
Wordfence’s 5 November follow-up gives the first full picture of the attack traffic against CVE-2026-119977, the race in full-package Core updates fixed in WordPress 7.1.4 and backports on 28 October. Attempts started on disclosure day with a handful of requests, rose sharply from 29 October, peaked on 30 October at more than 74,000 blocked in a day, and passed 240,000 in total. The requests go straight to the installer inside the predictable staging folder, for example the 6.9.11 package path below, in the hope of landing during the seconds an update is extracting:
shell
$ GET /wp-content/upgrade/wordpress-6.9.11/setup-config.php
If the installer answers, Wordfence says, the attacker can complete the staged installation, create an administrator for it and upload PHP, which is full control of the site. Its own note on the numbers is the one to repeat to anyone alarmed by them: a blocked request is an attempt, the window is short, and the attacker has to finish before the staging folder is removed, so successful exploitation is hard in practice. Nobody has published a confirmed compromise. CISA’s catalog lists the flaw from 3 November; Wordfence’s post gives 2 November.
Two practical points come out of the post. First, the update that installs 7.1.4 runs the old, vulnerable upgrade code one final time, so on a site still to be updated the deny rule goes in before the update, not after. Second, the Wordfence firewall can only see these requests when it is optimised and running in Extended Protection mode, because the staged installer does not load WordPress; premium users have had the rule since 28 October and free installs receive it on 27 November. A web-server rule covers everyone today.
Search for the staged installer and the published addresses
Read-only, for every site that ran a Core update since 28 October or is still to run one. Last week’s look-back still applies; these are the additions from Wordfence’s data.
01
Any request for PHP under the upgrade folder
Wordfence’s indicator is any external request for a PHP file under /wp-content/upgrade/, since no legitimate update makes one. On cPanel the per-domain logs are in domlogs:
Then read that domain’s log for the same address and the minutes around any update.
03
Leftovers, plugins and users
Between updates the upgrade folder holds only index.php. Review installed plugins and administrators for anything unexpected, with plugins skipped so nothing loaded can hide them:
shell
$ find /home/*/public_html/wp-content/upgrade -mindepth 1 -not-name index.php -ls$ wp user list --role=administrator--fields=ID,user_login,user_registered--skip-plugins--skip-themes$ wp plugin list --fields=name,status,version--skip-plugins--skip-themes
An administrator registered within minutes of an update, or a plugin nobody recognises, is the shape a successful staged install leaves.
My sites auto-update. Was I exposed to CVE-2026-119977 anyway?
Yes, during every full-package update they ever ran, and during the one that installed 7.1.4. The flaw is in the update process itself, so the exposure was the few seconds the extracted package sat in wp-content/upgrade/ with a predictable name. The attackers were polling for it from 28 October. Search the access logs for setup-config.php or install.php under that folder; a 200 is an incident, a 404 is a miss, and nothing at all is the usual result. Then deny the folder at the web server so the next update has no window.
Patchstack says the Core flaw is impractical and CISA says it is exploited. Which is right?
Both describe the same facts. The window is seconds long and the attacker has to guess the path within it, which is why Patchstack rates it low priority. Wordfence counted more than 18,500 attempts in 21 hours, which is why CISA lists it as exploited: the polling is real and cheap to run. Nobody has published a confirmed compromise. Update, deny the folder, read your logs, and do not spend the week arguing about the score.
Wordfence blocked 240,000 attempts. Does that mean 240,000 sites were hacked?
No. Those are requests its firewall stopped, mostly automated polling of the staging path in the hope of landing during an update. Wordfence itself says successful exploitation is difficult in practice, and nobody has published a confirmed compromise. The number says the path is being watched at scale, and your own access logs are the only evidence about your own sites.
Should I block the ten IP addresses Wordfence published?
Use them to search your logs; blocking them is harmless but not the fix. They are scanners, and the next ones will come from different addresses. The rule that stops all of them is a web-server deny on wp-content/upgrade/, which nothing legitimate ever requests over HTTP.
Choose the response path
Core is updated and the logs still show a hit: choose the response path.
The server under the sites
Get both halves of the PHP2Shell chain checked and proven on every host.
Best when several servers need PHP and the kernel verified from the running process rather than the repository, the Core update window and the published addresses searched in the logs, and the post-exploitation look-back done once, with a written result per host.
Get the finding classified and the site restored to a trusted state.
Best when an exploited booking, membership or form plugin left an administrator or a PHP file behind, a plugin with no fix was installed, or a cleaned site has come back, and you want every layer removed in one pass rather than one at a time.