Hack

WordPress Flaw CVE-2026-119977 Exploited: Patch and Lock Down

CISA says attackers are exploiting a WordPress core update race condition. Block the upgrade folder, update and check for compromise.

4 November 2026  ·  4 min read  ·  Anand

WordPress Flaw CVE-2026-119977 Exploited: Patch and Lock Down

On 3 November 2026, CISA added CVE-2026-119977 to its Known Exploited Vulnerabilities catalog, citing evidence of active exploitation. The flaw is a time-of-check time-of-use race condition in the WordPress core update process. WordPress fixed it on 28 October in version 7.1.4 and backported the fix to every branch that still gets security updates, back to 4.7. If any of your sites have not updated since then, treat this as urgent. The flaw is triggered during the core update itself, so the order you do things in matters.

How the flaw works

During a full-package core update, WordPress unpacks the new release into a temporary folder under wp-content/upgrade/. That folder sits inside the web root. Before the fix, the folder name was predictable. The staged copy also includes an installer script. An unauthenticated attacker who requests that script from the staging folder in the brief window before cleanup can reach PHP code execution.

In lab tests the window lasted only seconds, so attackers do not wait for it. They poll known paths automatically on many sites at once. Wordfence, which assigned the CVE, scores it 8.1 (High) because the timing is hard to hit. WordPress’s own advisory (GHSA-4w3m-c66w-69mg) rated it Low. With the CISA listing, the rating debate matters less: attackers are actively going after this flaw. Wordfence recorded more than 18,500 requests aimed at staged installer paths in the first 21 hours after it began watching. No network indicators, such as IP addresses or file hashes, have been published.

The fix adds a random 16-character suffix to the staging folder name. It also keeps an index.php in the upgrade folder and stops wp-config.php from being promoted out of the working directory.

Affected and fixed versions

Branch Affected Fixed in
7.1 7.1.0 to 7.1.3 7.1.4
7.0 7.0.0 to 7.0.7 7.0.8
6.9 6.9.0 to 6.9.10 6.9.11
6.8 6.8.0 to 6.8.11 6.8.12
6.7 6.7.0 to 6.7.10 6.7.11
6.6 6.6.0 to 6.6.10 6.6.11
4.7 to 6.5 Earlier point releases Latest point release of each branch
4.6 and older Unsupported No fix

One catch: you update to the fixed release using the old, vulnerable updater. That update can open the same window. Block web access to the staging folder first, then update.

Step 1: block web access to the upgrade folder

WordPress writes to wp-content/upgrade/ through the filesystem and never needs to serve it over HTTP, so blocking it at the web server is safe. On nginx, add this inside each WordPress server block. The ^~ modifier stops the PHP location from taking over these requests:

location ^~ /wp-content/upgrade/ {
    deny all;
}
sudo nginx -t && sudo systemctl reload nginx

On Apache, including cPanel servers, put this near the top of the site’s root .htaccess, above the WordPress rewrite block:

RewriteEngine On
RewriteRule ^wp-content/upgrade/ - [F,L]

Test it from outside. The response should be 403:

curl -I https://example.com/wp-content/upgrade/

Keep the rule in place permanently. A firewall plugin alone is not enough here, because the malicious request can reach the staged script without passing through WordPress. Wordfence says its own rule does not replace installing the update.

Step 2: update and verify

With WP-CLI, run these as the site’s own user:

wp core version
wp core update
wp core verify-checksums

On cPanel, WP Toolkit can update many installations at once. Afterwards, confirm each site reports a fixed version from the table above. Leave automatic background updates on for security releases. Give priority to sites where auto-updates are switched off, sites managed outside your normal patching, and anything on 4.6 or older, which needs a major upgrade.

Step 3: check for signs of compromise

Focus on the times when core updates ran on each site. Look for:

  • Requests to PHP files under wp-content/upgrade/, especially repeated polling
  • Administrator accounts you did not create
  • Plugins you did not install
  • PHP files the site owner did not put there
grep -E 'wp-content/upgrade/.*php' /var/log/nginx/access.log*
wp user list --role=administrator --fields=ID,user_login,user_registered
wp plugin list
find wp-content/uploads -name '*.php'

On Apache, search the domain’s access logs instead. Use zgrep for rotated, compressed logs. If you find anything suspicious, take the site offline, preserve the logs, change every password and key, and restore from a clean backup rather than cleaning files by hand.

How TechProvidence can help

TechProvidence manages WordPress hosting and maintenance on cPanel, nginx and Apache servers. That covers fleet-wide core updates, web server hardening, log review and incident clean-up. If you run many WordPress sites and want them patched and checked quickly, contact us.

Source: CISA

Running into something similar?

We look after Linux servers, control panels and virtualization for businesses every day. If an update, vulnerability or outage here affects you, we can help.