•

WordPress update-process flaw is under attack: update to 7.1.4

A flaw in the way WordPress updates itself is being actively probed by attackers. It affects every WordPress version from 4.7 to 7.1.3, it needs no login to attempt, and it was fixed in WordPress 7.1.4 on 28 October 2026. Security firm Wordfence says its firewall has blocked more than 240,000 attempts to exploit it since the day of disclosure. If your site has not updated yet, now is the time.

Key takeaways

  • The flaw (CVE-2026-119977) lets an attacker run code on the server during the few seconds a full WordPress core update is in progress.
  • It affects WordPress 4.7 to 7.1.3. The fix is 7.1.4, or the matching patched release for older branches.
  • The 240,000 figure is a running total of blocked requests since 28 October, not a rate per minute or hour. It does not mean 240,000 sites were hacked.
  • Sites with automatic background updates should already be patched. Check rather than assume.

What the flaw is

When WordPress runs a full core update, it unpacks the new version into a folder under wp-content/upgrade/. Before 7.1.4, that folder had a predictable name and could be reached from the web. According to Patchstack’s analysis, the unpacked copy includes WordPress’s installer, which can be started without the site’s own configuration. An attacker who requests the right address during the update can run that installer, create an administrator account and upload their own code.

That timing is the catch. This is a race condition: the attacker has to get a request in during the short window while the update is running, and finish before the folder is cleaned up. Both Wordfence and Patchstack describe it as difficult to exploit in practice. The two firms differ on how to rate it: Wordfence scores it 8.1 (High), while Patchstack gives it a low priority because of how small the window is. No account or user action is needed to try it, and the window comes round on every core update, including unattended ones.

The official WordPress 7.1.4 announcement credits the discovery to researcher Umut Bayram and says site owners should update immediately. The same release fixes a long list of other issues, mostly stored cross-site scripting bugs in blocks, the Interactivity API and the Customizer, which Patchstack counts as 22 vulnerabilities in total.

How many attacks, and what the number means

In its report of 5 November, Wordfence says attackers began targeting the flaw on 28 October, the day it was disclosed, and that its firewall has blocked over 240,000 exploit attempts since. Activity peaked between 29 October and 1 November, with more than 74,000 attempts blocked on 30 October alone.

So the figure is a total covering the period from disclosure to that report, not a rate, and it counts requests that were stopped. Wordfence is clear that a large number of blocked requests does not mean a large number of sites were successfully attacked. Most of it looks like automated probing of the predictable folder, hoping to catch a site mid-update. Even so, the US cyber agency CISA has added the flaw to its Known Exploited Vulnerabilities catalogue, which it does only on evidence of active exploitation.

What to do now

  1. Check your version. In WordPress, go to Dashboard, then Updates. You want 7.1.4, or the patched release for your branch (for example 7.0.8, 6.9.11 or 6.8.12). Branches back to 4.7 have a fix; 4.6 and earlier get nothing, so those sites need a proper upgrade.
  2. Update, and don’t put it off. Updating from a vulnerable version runs the old upgrade process one last time. Wordfence’s view is that this single short window is still better than leaving the site unpatched, and that once you are on a fixed version later updates are no longer exposed.
  3. Block the folder if you can. Patchstack advises denying web access to wp-content/upgrade/ at the server level, and Wordfence suggests blocking PHP files there before you update. This is a job for your host or developer, because it is a server setting rather than a WordPress one.
  4. Look for signs of a visit. Between updates, that folder should hold nothing but an index.php. Leftover folders are worth investigating. Check your server access logs for requests to PHP files under /wp-content/upgrade/, especially setup-config.php, and review your administrator accounts and installed plugins for anything you do not recognise.

A security plugin alone will not cover this

Patchstack points out that the request goes to files in the unpacked folder, which load WordPress from their own copy rather than from your site. Protection that runs inside WordPress therefore never gets a look in. Wordfence says its firewall can block it only when it is optimised and running in Extended Protection mode, and that its free version gets the rule on 27 November, 30 days after paid users. The reliable fix is the update itself, with the server-level block as an extra layer.

If you think you were affected

An absence of log entries does not prove a clean site, and a handful of requests in your logs does not prove a break-in. If you find unexpected administrator accounts, unfamiliar plugins or files you did not add, take a backup of the current state, then remove them and review the site for backdoors. If the site has been hacked, WebsiteFix handles clean-up and recovery.

If you would rather someone checked for you, a WordPress security audit covers versions, update settings, server exposure and user accounts, and ongoing WordPress support keeps updates, backups and monitoring in hand so that a fix like this one is applied the day it ships.

Sources