WordPress CVE-2026-119977: When the Update Window Becomes the Attack Window

A race condition in the WordPress core updater, fixed in 7.1.4, is now on CISA's Known Exploited list. WordPress calls it Low, Wordfence calls it High. Who to believe, and the six things to check on every site.

The short answer: CVE-2026-119977 is a race condition in the WordPress core updater, present from version 4.7 through 7.1.3. While an update is running, files briefly sit in a staging directory where a well-timed request can execute code. It is fixed in WordPress 7.1.4, released October 28, 2026, and CISA added it to its Known Exploited Vulnerabilities catalog on November 3. Update to 7.1.4, block web access to wp-content/upgrade/, and check that the PHP underneath is patched too.

This one is worth a post of its own for two reasons. It turns the act of patching into the moment of exposure, which is uncomfortable for anyone who tells small businesses “just keep it updated.” And the people who should know disagree sharply about how serious it is.

How the flaw works, without the jargon

When WordPress updates itself, it downloads the new files, unpacks them into a temporary folder inside wp-content/upgrade/, and then copies them into place. For a few seconds, some of those files can be requested directly from the web. If an attacker’s request lands in exactly that window, the server runs code it shouldn’t.

That is a time-of-check to time-of-use race: the system checks that things are safe, then acts a moment later, and the attacker squeezes in between. It’s hard to win once. It gets a lot easier when automated scanners hammer the staging paths of thousands of sites around the time a release ships, which is what Wordfence reported seeing from release day.

Low, High, or Known Exploited? Who to believe

WhoRatingWhy
WordPress security teamLowExploitation requires winning a narrow race while an update is running
Wordfence (the CVE Numbering Authority)CVSS 8.1, HighA successful attempt gives an unauthenticated attacker code execution
CISAKnown Exploited Vulnerabilities catalog, added November 3Evidence of active exploitation in the wild

All three are reasonable from where they sit. WordPress is describing how hard the race is to win against a single site. Wordfence is describing how bad the outcome is when it is won. CISA is describing what attackers are actually doing.

For prioritization, the last one wins. A severity score describes a flaw in the abstract. Evidence of exploitation describes your Tuesday. As we argued in Attack-Path Analysis: Why Isolated CVEs Miss Your Real Risk, real priority comes from combining severity, exploitation, and exposure. An internet-facing WordPress site with a KEV-listed flaw is at the top of the list regardless of whether the vendor called it Low.

Reported attack volumes vary by source, and as of early November we had found no confirmed compromise publicly tied to this flaw. That is a reason to act calmly, not a reason to wait.

What to do

Update core to WordPress 7.1.4 or later

Critical

Check Dashboard → Updates on every site, including staging, microsites, and the campaign site nobody has logged into since spring. Confirm the version afterward rather than assuming the auto-update ran.

Block web access to wp-content/upgrade/

Critical

Nothing in the upgrade staging directory needs to be served to visitors. A web-server or CDN rule that denies requests to that path removes the attack window even on a site you can't update today.

Look for leftovers

High

Review wp-content/upgrade/ and the web root for PHP files you don't recognize, and check for new administrator accounts created since late October.

Know which protection actually covers it

High

Because the request can hit a staged PHP file directly, a plugin-level firewall that only loads with WordPress may never see it. Confirm your WAF runs in front of PHP, at the server or edge.

Confirm the PHP underneath is patched too

High

A patched WordPress on an unpatched PHP runtime is still exposed to PHP2Shell. Check both layers together.

Turn on (and monitor) automatic core updates

Medium

Minor-release auto-updates are on by default but are often disabled by hosts or plugins. Make sure they run, and that someone gets an email when they fail.

If someone else runs your site

Most small businesses don’t patch their own WordPress. An agency, a freelancer, or a managed host does. Send them three questions:

  1. Are all of our WordPress sites, including staging, on 7.1.4 or later?
  2. Is web access to wp-content/upgrade/ blocked at the server or CDN?
  3. Which PHP version do our sites run, and does it include the October 21 PHP2Shell fixes?

Ask for the answer in writing, with the version numbers. That email is also your evidence if an auditor or insurer asks later how you responded to a known-exploited vulnerability.

The bigger lesson: updates are part of your attack surface

It’s tempting to treat updates as purely good news. This flaw is a reminder that an update is a process with its own moving parts: temporary files, permissions, and a window where the system is half old and half new. The practical response is not to update less. It is to make sure the places updates touch, like staging directories, aren’t reachable from the internet in the first place, so the window doesn’t matter.

Check Your WordPress and PHP Together

The PHP Exposure Assessment reports which PHP version your site runs, whether it carries the latest fixes, and the configuration and exposed-file issues that make any flaw easier to reach. Scan Ninja's platform then keeps watching for the next known-exploited issue and ranks it by real exposure.

Or talk to our team

Sources

Related Resources