THE SHORT ANSWER
WordPress 7.1.4 (released October 28, 2026) fixes CVE-2026-119977, a flaw in the core updater that can allow code execution during the few seconds an update is unpacked in wp-content/upgrade. Before you update, block web access to /wp-content/upgrade/ in the server config or root .htaccess and confirm it returns 403. Then update to 7.1.4 or your branch's fixed release and check for unknown admins and stray PHP files.
WordPress 7.1.4 is a security release with more than a dozen fixes. One of them is unusual: the weak spot is the update process itself. While WordPress unpacks a new version, a copy of the installer sits for a moment inside wp-content/upgrade. The old, unpatched updater does that unpacking, so the very update that fixes the flaw can open the window one last time.
Wordfence reported attack attempts against this window within minutes of publishing its firewall rule, and CISA added the flaw to its Known Exploited Vulnerabilities list in early November. If you look after client sites, this is the one to handle in the right order: block, update, confirm, check.
Applies to: WordPress 4.7 to 7.1.3 (affected), fixed in 7.1.4 and matching branch releases. Apache, LiteSpeed and Nginx. Last verified: November 2026.
01Quick reference
| Error | Most likely cause | Try first |
|---|---|---|
| Folder not blocked | Rule missing or below the WordPress block | Add the deny rule at the top of .htaccess |
| Nginx ignores .htaccess | Rule added in the wrong place | Add a location block, reload |
| Still on an old version | Auto updates off or failed | Update manually, then confirm |
| Update lock stuck | A failed earlier update | Wait, or delete the lock option |
02What the flaw is and which versions are affected
The CVE record lists every WordPress version from 4.7 through 7.1.3 as affected. WordPress shipped fixed releases for each supported branch on October 28, 2026. WordPress 4.6 and older get no security fixes at all, so those sites need a full upgrade.
WordPress rates the issue low in its own advisory. Wordfence, which issued the CVE, scores it 8.1 (high). The window lasts only seconds, so an attack is hard to time, but it needs no login. The practical answer is the same either way: patch now, and close the folder first.
| Your branch | Fixed release |
|---|---|
| 7.1 | 7.1.4 |
| 7.0 | 7.0.8 |
| 6.9 | 6.9.11 |
| 6.8 | 6.8.12 |
| 6.7 | 6.7.11 |
| 6.6 | 6.6.11 |
| 6.5 | 6.5.14 |
| 6.4 | 6.4.14 |
| 4.7 to 6.3 | A fixed point release per branch (see the HelpHub list) |
| 4.6 and older | None. Upgrade to a supported branch |
Automatic background updates use the same updater and the same steps, so a site that patched itself overnight also went through the window once. That is why the checks in the last section matter even if the site already shows 7.1.4.
Still broken after these steps?
Send us the URL and the exact error. Fixes start from $59, with a fixed quote within 24 hours and an NDA if you need it.
03The safe update order, step by step
- Take a backup of files and the database. See our backup first step.
- Block web access to
/wp-content/upgrade/in the server config, or in the.htaccessfile in the WordPress root (rules below). - Confirm the block. Open
https://yoursite.com/wp-content/upgrade/in a private window. It must return 403 Forbidden, not 200 or 404. - Update from Dashboard, Updates, or let the background update run.
- Confirm the version in Dashboard, Updates or with
wp core version. - Check the site for signs that anything got in during the window.
- Leave the block in place. WordPress reads and writes that folder on disk, not over the web, so updates keep working.
Do not put an .htaccess file inside wp-content/upgrade. The old updater clears that folder before it unpacks a package, so the file is gone at the exact moment you need it. The rule has to live in the server config or the root .htaccess.
If you would rather avoid the window entirely, a manual update done outside the web root works: unpack the release in a folder the web server does not serve, copy the core files over (leave wp-config.php and wp-content alone), then run the database update. wp core update is not a substitute here, because WP-CLI calls the same updater and unpacks into the same folder.
04Problems you may hit while patching
/wp-content/upgrade/ returns 200 or 404 instead of 403
Quick fix: Add a deny rule for the folder in the root .htaccess, above the WordPress block.
Why it happens: Nothing blocks the folder yet, the rule sits below the WordPress rewrite block, or the server ignores .htaccess.
- Open the
.htaccessfile in the folder that holdswp-config.php. - Paste the rule below at the very top, above the
# BEGIN WordPressline. - Save, then clear any page cache (LiteSpeed Cache, Cloudflare) so you are not looking at a cached response.
- Reload
/wp-content/upgrade/in a private window and confirm 403. - If you still get 200, your server may not read .htaccess. Use the Nginx rule in the next item, or ask the host to add the block.
# Block web access to the core update staging folder
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule ^wp-content/upgrade/ - [F,L]
</IfModule>The [F] flag is Apache's standard way to send 403 Forbidden, and LiteSpeed reads the same rewrite rules. The Hacker News write-up also gives a one-line alternative: RedirectMatch 403 ^/wp-content/upgrade/. Use one, not both.
The .htaccess rule does nothing (Nginx server)
Quick fix: Nginx never reads .htaccess. Add a location block in the site's server config and reload Nginx.
Why it happens: Nginx only uses its own config files, so rules in .htaccess have no effect.
- Open the server block for the site (on managed hosting, ask support to add it).
- Add the location block below inside the
server { }block. - Test the config with
nginx -t, then reload Nginx. - Confirm
/wp-content/upgrade/now returns 403. - On Apache with access to the virtual host, the equivalent is
Require all deniedin a Directory block for that folder.
location ^~ /wp-content/upgrade/ {
deny all;
}Site still shows WordPress 7.1.3 or older after updating
Quick fix: Run the update again from Dashboard, Updates and confirm with wp core version. Older branches get their own fixed release.
Why it happens: Background updates are turned off, the update failed quietly, or the site is on an older branch that receives its own point release instead of 7.1.4.
- Go to Dashboard, Updates and click Check again.
- Compare your version with the fixed release table above. A 6.8 site is fixed by 6.8.12, not 7.1.4.
- If background updates are off, check
wp-config.phpforAUTOMATIC_UPDATER_DISABLEDorWP_AUTO_UPDATE_COREset to false. - Run the update manually, with the folder already blocked.
- Confirm the result with the command below.
wp core version
wp core check-updateAnother update is currently in progress
Quick fix: An earlier core update left its lock behind. Wait 15 minutes, or delete the core_updater.lock option.
Why it happens: WordPress sets a lock while it updates core. If that update crashed or timed out, the lock stays until it expires.
- Wait about 15 minutes. The lock expires on its own.
- If you cannot wait, delete the lock with WP-CLI (below) or remove the
core_updater.lockrow from the options table in phpMyAdmin. - Run the update again.
- If it keeps failing, read the server error log. See our full fix for this error.
wp option delete core_updater.lock05Check that nothing got in during the window
Do this on every site that ran an affected version after October 28, including sites that updated themselves. Wordfence's advice, as reported by The Hacker News, comes down to four things.
- Look in the access logs for requests to PHP files under
/wp-content/upgrade/, especially any that returned 200. - List administrators with
wp user list --role=administratorand remove any account you do not recognize. - Look for plugins nobody installed, and for PHP files inside
wp-content/upgradethat nobody put there. On a clean site that folder is normally empty or holds only leftover package folders. - Run
wp core verify-checksumsto confirm core files match the official release.
If any of these turn up something odd, treat the site as compromised and follow our first 60 minutes plan for a hacked site. Save the logs before you clean anything.
A note on firewalls: secondary reports say the malicious request goes straight to a PHP file without loading WordPress, so a plugin firewall only sees it when it runs before WordPress (for Wordfence, Extended Protection). A server or edge rule, like the ones above or a Cloudflare WAF rule, does not depend on that.
06If you manage many client sites
Agencies feel this one most, because background updates patched many sites before anyone added a block. A simple order works:
- Add the deny rule to every site first, through your management tool or a shared server config.
- Then push updates, branch by branch, to the fixed release for each.
- Run
wp core versionandwp user list --role=administratoracross the fleet and log the output. - Flag any site still on 4.6 or older for an upgrade quote. It will not get this fix.
This is routine work in our white label maintenance plans. If a client site is already showing problems, our WordPress error fix service can patch and check it under your brand.
Need the full list? See our WordPress errors fix guide and the hosting, PHP and cPanel errors guide.
More fixes
07FAQ
Is it safe to just click Update to 7.1.4?
It works, but the update itself is unpacked by the old updater, so it opens the window one last time. Block web access to /wp-content/upgrade/ first, confirm it returns 403, then update.
My site already updated itself to 7.1.4. Am I fine?
The flaw is closed, but the automatic update went through the same window. Check the access logs for requests to PHP files in wp-content/upgrade, list administrator accounts and run wp core verify-checksums.
Will blocking wp-content/upgrade break future updates?
No. WordPress works with that folder on disk. The rule only stops browsers and bots from requesting files in it over the web, so you can leave it in place.
I am on WordPress 6.8. Do I have to jump to 7.1?
No. Each supported branch got its own fixed release, for example 6.8.12 for 6.8 and 7.0.8 for 7.0. Sites on 4.6 or older get no fix and need a real upgrade.
Does wp core update avoid the problem?
No. WP-CLI uses the same core updater and unpacks into the same folder. Add the block first, or do a manual update from a folder the web server does not serve.
Why does WordPress call it low severity when others say high?
WordPress's own advisory rates it low. The window lasts only seconds, which makes an attack hard to time. Wordfence scores it 8.1 because it needs no login and can lead to code execution. Both say to patch now.
SOURCES
- WordPress 7.1.4 release announcement (WordPress.org)
- WordPress 7.1.4 version notes and fixed releases per branch (HelpHub)
- Installing the fix for an exploited WordPress flaw can expose some sites one last time (The Hacker News)
- WordPress Core 7.1.4 fixes an upgrade-window race RCE (Rescana)
- wp core verify-checksums (WP-CLI handbook)






