WordPress CVE-2026-119977: Upgrade-Window RCE Now in CISA KEV
What happened
On November 3, 2026, CISA added CVE-2026-119977 to its Known Exploited Vulnerabilities (KEV) catalog. The entry is titled as a WordPress Core Time-of-check Time-of-use (TOCTOU) race condition, and CISA cited evidence of active exploitation. BleepingComputer reported that Federal Civilian Executive Branch agencies must remediate by Friday, November 6, under Binding Operational Directive 26-04.
The timeline from public reporting:
- October 28: The WordPress security team shipped WordPress 7.1.4. It described the fix as addressing a weakness in the upgrade process that can lead to remote code execution during the upgrade window. Fixes were backported to every eligible branch down to 4.7.
- October 28-31: Wordfence, which is listed as the CNA scoring the flaw, reported heavy probing soon after disclosure. One write-up cites more than 18,500 requests in the first 21 hours aimed at staged
setup-config.phpinstaller paths. Another cites 60,471 blocked attacks in 24 hours as of October 31. Neither write-up reports confirmed compromises. - October 30: Honeypot telemetry cited by The Hacker News, as relayed by SOC Prime, recorded exploitation attempts.
- November 3: CISA added the CVE to KEV.
- Weekend before KEV listing: Wordfence updated its advisory to say it had blocked 13,095 attacks against the flaw in the previous 24 hours, according to BleepingComputer.
The researcher credited with the report is Umut Bayram of Picus Security. The Wordfence figures vary by reporting window, so they should not be added together or treated as a count of victims.
What is not confirmed
- Victim count: No public source reports how many sites were actually compromised.
- Attribution: No threat actor or campaign has been named. CISA gave no detail on who is exploiting the flaw or what they do after getting code execution.
- Ransomware use: One tracker lists ransomware use as not confirmed.
- IOCs: Public reporting indicates no IP addresses, hashes or other indicators have been published by CISA, WordPress or Wordfence. What exists is a URL pattern, covered below.
- Severity scoring: Sources disagree. Wordfence scores it CVSS 8.1 (High), while one write-up says WordPress itself rated it Low. The WordPress announcement reportedly carried no CVE number.
Who is affected
WordPress Core versions 4.7 through 7.1.3 are affected. This is a core issue, not a plugin or theme flaw. Versions 4.6 and earlier get no fix at all.
Patched releases reported across sources: 7.1.4, 7.0.8, 6.9.11, 6.8.12, 6.7.11, 6.6.11 and 4.7.39. Teams should check the WordPress release archive for the exact fixed version on any other branch. Running an older branch's latest point release is the correct target. WordPress has stressed that only the newest release is actively supported, so backports should be treated as a stopgap.
Exposure is narrower than the version range suggests. Based on the Wordfence-derived descriptions, exploitation needs:
- a core update in progress, and specifically a full-package core upgrade;
- a staging directory under
wp-content/upgrade/that the web server serves; - PHP execution allowed in that directory;
- a staging path the attacker can predict or discover.
Public reporting does not give a sector or regional breakdown. In practice, the sites most at risk are internet-facing WordPress installs with auto-updates enabled that sit on hosts where wp-content/upgrade/ is reachable. Managed hosts and plugin update flows may differ from the default layout and should be verified, not assumed.
How the attack works
During a full-package core upgrade, affected versions unpack the new release into a predictable directory beneath wp-content/upgrade/. That staged copy is a complete WordPress tree, including the installer flow around wp-admin/setup-config.php. WordPress then copies the files over the live installation and deletes the staging folder.
The race: while the staged files exist, an unauthenticated attacker can request the staged installer directly over HTTP. Wordfence says the exploit requests a staged PHP file directly, without first loading WordPress. In effect the site's own installer becomes reachable before it is promoted or cleaned up. The CVE record is a TOCTOU weakness, a mismatch between when the state is checked and when it is used. Wordfence says the 7.1.4 fix randomizes the staging directory name, adds an index guard, and prevents unsafe promotion of staged configuration data.
Observed attacker behavior is consistent with timing attacks. Wordfence data cited in one write-up shows two of the largest sources repeatedly polling small groups of sites for about 14.5 hours, which fits an attempt to catch short update windows. Other sources tried variations of staging-directory and version names, and Wordfence notes that not every request used the exact vulnerable path.
Post-exploitation is not documented for this CVE. Public reporting does not say what attackers do once they have code execution, such as installing webshells, creating admin users or modifying wp-config.php. Wordfence's own guidance for unpatched sites points at unfamiliar administrator accounts, unexpected plugins and unrecognized PHP files, but that is a checklist and not a description of observed activity.
MITRE ATT&CK mapping
- T1190 – Exploit Public-Facing Application: the core technique, since the target is internet-reachable WordPress.
- T1595.002 – Active Scanning: Vulnerability Scanning: fits the mass polling of staging paths reported by Wordfence.
- T1505.003 – Server Software Component: Web Shell: a plausible follow-on that applies only if a shell is dropped. This is not confirmed for this campaign.
Indicators
- CVE: CVE-2026-119977.
- URL patterns (behavioral, not attacker-specific):
/wp-content/upgrade/and/wp-content/upgrade/*/setup-config.php. - IPs, hashes, domains, user agents: none published as of this writing.
Do not confuse this with the earlier "wp2shell" chain (CVE-2026-63030 and CVE-2026-60137), which was added to KEV in July and affects the 6.8 through 7.0 branches by a different mechanism. Another WordPress Core file-inclusion flaw, CVE-2026-87902, is also in KEV. Sites patched against those are not automatically patched against this one.
Detection guidance for defenders
The detection logic is straightforward. WordPress's updater writes to wp-content/upgrade/ using the filesystem, so legitimate HTTP requests to that path should essentially never appear. Any request for a PHP file there is suspicious. Some caveats:
- The signal is most meaningful in web server or CDN/WAF logs. Keep access logs long enough to answer whether anyone touched that path around a past update.
- A request that returned 200 or 302 is far more concerning than a 403 or 404. Check the response codes and byte counts, and compare timing against your update history.
- After the November 3 listing, expect heavy scanner noise. Prioritize hits on sites that updated during the window.
Example hunt: IIS or reverse-proxy logs (KQL)
W3CIISLog
| where TimeGenerated > ago(30d)
| where csUriStem has "/wp-content/upgrade/" and csUriStem endswith ".php"
| summarize Hits=count(), Statuses=make_set(scStatus), FirstSeen=min(TimeGenerated), LastSeen=max(TimeGenerated) by cIP, sSiteName, csUriStem
| order by Hits descThis finds sources requesting PHP files in the WordPress upgrade staging tree over 30 days. Any 200 in Statuses deserves immediate triage. Adapt the table and column names for Apache or nginx logs, or for your WAF's schema.
Example hunt: Linux web servers
zgrep -hE 'wp-content/upgrade/.*\.php' /var/log/nginx/*access*.log* \
| awk '{print $1, $7, $9}' | sort | uniq -c | sort -rn | head -20This lists client IPs, requested paths and status codes for PHP requests into the staging tree, ranked by volume.
Host and EDR checks
- Look for PHP files you did not place in
wp-admin/,wp-includes/, the site root andwp-content/. Compare core files against official WordPress.org checksums (for example withwp core verify-checksums). - Check for new administrator accounts, unexpected plugins, and recent modifications to
wp-config.php. - Alert on the web server user (
www-data,apache,nginx) spawning shells or network tools, which would indicate a webshell or command execution. - Review database connection changes. The fix mentions unsafe promotion of staged configuration data, so an unexpected
wp-config.phppointing at an attacker-controlled database is worth ruling out.
Mitigation and response
- Patch now. Move to 7.1.4, or to the fixed release for your branch (for example 7.0.8, 6.9.11, 6.8.12, 6.7.11, 6.6.11, 4.7.39). Confirm the version installed on each site and do not rely on auto-update having finished. If you can, migrate to the current supported release and avoid relying on backports.
- Block the path before and during updates. At the web server, WAF or CDN, deny HTTP access to
/wp-content/upgrade/and disable PHP execution there. One nginx example uses alocation ^~ /wp-content/upgrade/block that returns 403. Test on a staging copy first, since some hosts and update flows use different paths. One write-up claims blocking PHP execution fully mitigates the flaw even on unpatched versions. Treat that as strong hardening and not a reason to skip the patch. - Schedule updates deliberately. For unpatched sites that must be updated, apply the deny rule first, update, then verify that the staging folder has been cleaned up.
- Hunt retrospectively. Run the queries above across at least the period since October 28, and longer if logs allow.
- If you find a successful hit: isolate the host, preserve logs and a disk image, and rebuild from known-good core files. Rotate WordPress admin passwords, database credentials and the salts and keys in
wp-config.php. Review users, plugins, scheduled tasks (wp-cronentries and system cron) and any other sites on the same hosting account. - Inventory. Find forgotten WordPress instances, including marketing sites, staging copies and acquired domains. These are the usual victims of KEV-listed WordPress bugs.
US federal agencies and their contractors have a hard deadline of November 6. Other organizations should use that date as a benchmark.
What individuals should do
This flaw is a server-side issue, so visitors to a WordPress site have nothing to patch. People who run their own WordPress site, such as a blog or small business page, should update to the latest release immediately and confirm the version in the dashboard. They should also ask their host whether wp-content/upgrade/ is blocked from web access. If a site is compromised, change the admin passwords, use a unique password for each account, and check the user list for accounts they do not recognize.
FAQ
Does this affect every WordPress site all the time?
No. The exposure arises during a core upgrade, when the staged installer files exist on disk. The site also needs a web-reachable, executable staging path. Attackers are reportedly polling continuously to catch that window, so a site that updates regularly is still a target.
Is there a public exploit or attribution?
Wordfence and others describe observed exploit traffic, and CISA confirmed exploitation. Public reporting does not name an actor, publish IOCs, or describe what happens after exploitation. Whether a public proof of concept exists is not established in the sources reviewed.
Is updating to 7.1.4 enough?
It fixes the root cause by randomizing the staging directory and adding guards. It does not tell you whether the site was already compromised. If the site was unpatched and exposed since October 28, check logs and files for signs of exploitation, and keep the path blocked as a second layer.
Bottom line
This is a real, confirmed-exploited core RCE, but it has narrow preconditions, and the only hard numbers so far are scanning volumes, not confirmed compromises. The risk is highest for unpatched, auto-updating sites on hosts that expose wp-content/upgrade/. The fix and the web-server workaround are both simple, so it should be handled as a same-week job, with log review included.
Original reporting: BleepingComputer
Protect yourself with tools recommended by cybersecurity professionals:
The tools below are independently selected based on security audits, transparency, and real-world effectiveness.