Ackatec
All insights

WordPress Upgrade-Window RCE Is on CISA's KEV: Patch Core and Check for Compromise

CVE-2026-119977 is on CISA's KEV after active probing. How to patch WordPress, block the staging path, and check whether an upgrade window was abused.

Author
Ackatec
Published
Reading time
6 min read
  • WordPress
  • Application security
  • Vulnerability management
  • CISA KEV
  • Penetration testing
  • Incident readiness

On November 3, 2026, CISA added CVE-2026-119977 (opens in a new tab) to its Known Exploited Vulnerabilities catalog. The flaw is a time-of-check time-of-use race in WordPress Core that can give an unauthenticated attacker remote code execution while a full-package core upgrade is running. Federal agencies had until November 6, 2026 to remediate it under BOD 26-04 (opens in a new tab), and CISA's KEV entry also expects forensic triage.

The short answer: confirm every WordPress site is on 7.1.4 or the fixed release for its branch, deny web access to wp-content/upgrade/ at the server, and review logs and the site itself for signs that an attacker hit the upgrade window before you patched.

What is CVE-2026-119977?

CVE-2026-119977 is an unauthenticated remote code execution vulnerability in WordPress Core versions 4.7 through 7.1.3. Wordfence (opens in a new tab), the CVE Numbering Authority for this issue, scores it CVSS 3.1 8.1 (High) with high attack complexity. The weakness is CWE-367: a race condition during the upgrade process.

WordPress shipped the fix in version 7.1.4 (opens in a new tab) on October 28, 2026, and backported security releases through the 4.7 branch. The WordPress security team described it as a weakness in the upgrade process that can lead to remote code execution during the upgrade window, reported by Umut Bayram of Picus Security.

How does the upgrade-window race work?

During a full-package core update, affected WordPress versions unpack the new files into a predictable directory under wp-content/upgrade. That temporary copy can include the WordPress installer. On many servers the staging tree is reachable over the web, so an attacker who requests a staged installer file such as setup-config.php at the right moment can interact with that copy and progress to PHP code execution.

Wordfence lists four conditions for a successful attack: a full-package update that includes installer files, public web and PHP access to the staging tree, a predictable or discovered staging path, and enough time to finish before WordPress cleans up. In lab environments, Wordfence observed that the vulnerable directory normally remained available for only seconds. A one-off request is unlikely to win; repeated automated polling is how attackers improve their odds.

Is CVE-2026-119977 being exploited?

Yes, in the sense of active probing and attempted exploitation. Wordfence reported that the first match for its new firewall rule arrived nine minutes after deployment, and that during the first 21 hours it recorded more than 18,500 requests targeting staged setup-config.php installer paths. In a November 2026 follow-up (opens in a new tab), Wordfence said its firewall had already blocked over 240,000 exploit attempts. CISA's November 3 KEV addition is based on evidence of active exploitation.

Treat those numbers as attempt volume, not confirmed takeovers. Wordfence notes that most requests are automated polls hoping to catch an upgrade in progress, and that successful remote code execution remains difficult in practice. Still, a marketing site, careers page, or customer portal that sits outside your normal patch cadence is exactly the kind of asset attackers poll for.

Which WordPress versions are fixed?

Install 7.1.4 or later when you can. If you must stay on an older branch for a short time, use the matching security release WordPress backported for that branch. Wordfence's patched list includes 7.1.4, 7.0.8, 6.9.11, 6.8.12, 6.7.11, 6.6.11, 6.5.14, 6.4.14, and further backports through 4.7.39. Versions older than 4.7 are outside the courtesy backport range and no longer receive security updates from WordPress.

Confirm the version rather than assuming automatic updates finished. WordPress says sites that support automatic background updates should begin updating on their own, but that does not cover every host, agency-run site, or install where automatic updates were turned off.

What should you do this week?

1. Inventory every WordPress site you own or fund

Include marketing sites, microsites, documentation hubs, careers pages, and any site an agency or host runs on your behalf. Those often fall outside the same patch and monitoring process as your product or corporate apps. A security assessment that maps internet-facing content management systems is a practical way to close that gap when the inventory is incomplete.

2. Block web access to the upgrade staging path, then patch

Deny HTTP access to PHP under wp-content/upgrade/ at the web server or virtual host before you update. WordPress only needs filesystem access to that folder. Put the rule in server configuration or site-root .htaccess, not inside the upgrade folder itself, because older versions wipe that directory before each unpack.

Then install the fixed release for each site. Wordfence still recommends updating promptly even though the last upgrade from a vulnerable build runs the vulnerable process one more time: the window is short, and once the site is patched, later upgrades are no longer affected. A WordPress security plugin alone is not enough. Wordfence warns that the malicious request can hit a staged PHP file without loading WordPress first, so a PHP-level firewall may never see it unless Extended Protection is in place, and a firewall rule does not replace the security update.

3. Hunt for compromise around recent upgrade windows

Patching closes the race for future updates. It does not undo a foothold planted during an earlier window. Review access logs for unexpected requests to PHP files under wp-content/upgrade/, especially repeated polling for setup-config.php or version-named staging paths. On the site itself, look for unfamiliar administrator accounts, unexpected plugins, and PHP files you did not place there. Focus on the times when core updates ran.

That hunt matches what CISA expects after KEV flaws that can grant total control of an internet-facing asset. For the broader federal remediation model behind this listing, see our post on BOD 26-04 and the December 7 deadline. If logs or the site show a hit, treat it as an incident: isolate, preserve evidence, and bring in incident readiness support before you wipe and rebuild.

4. Test the long tail the way an attacker would

Once the emergency patching is done, an authorized penetration test scoped to your public WordPress estate can show whether staging paths are still web-reachable, whether old branches remain online, and whether content or plugin weaknesses would let an attacker stay after a successful foothold. Pair that with a short inventory of which sites still run unsupported releases. CVE-2026-119977 is not the same as PHP2Shell, but both remind you that the PHP and CMS layer on marketing infrastructure deserves the same urgency as edge devices.

Questions to answer this week

  1. Which public sites run WordPress, including sites run by agencies or hosts?
  2. Is every one of them on 7.1.4 or the fixed release for its branch?
  3. Is wp-content/upgrade/ denied at the web server before the next core update?
  4. Would our logs show repeated requests for staged installer paths during upgrades?
  5. Who owns hunting for unexpected admins, plugins, or PHP files after a KEV listing?

If those answers are unclear, talk with Ackatec about inventory, assessment, and incident readiness for content sites that sit outside your main application stack. Acting on these steps reduces risk but does not guarantee that no compromise occurred or will occur.

References