Security 8 min read ·
WordPress 7.1.4 Security Update: What CVE-2026-119977 Means for You
WordPress security update 7.1.4 fixes 22 flaws, including the exploited CVE-2026-119977. Check your version, patch safely and look for signs of a hack.
WordPress 7.1.4, released on 28 October 2026, fixes 22 security problems. The serious one is CVE-2026-119977, a race condition during core updates that can let an attacker with no account run code on your server. Attackers started probing for it the same day, and the US agency CISA added it to its list of actively exploited flaws on 3 November 2026. Update to 7.1.4, or to the fixed release for your branch, such as 7.0.8 or 6.9.11: WordPress backported fixes to every branch down to 4.7. Then block web access to /wp-content/upgrade/ and check for admin users and PHP files you don't recognise.
The short version, as of 15 November 2026:
- Check your version under Tools, Site Health, Info, or run
wp core version. - Take a backup, block
/wp-content/upgrade/if your server allows it, then update. - If your site was out of date after 28 October, go through the compromise checklist below.
- If you use Elementor Pro, make sure it's on 4.2.2 or newer, because a separate flaw in its forms is also being exploited.
What does the WordPress 7.1.4 security update fix?
The WordPress 7.1.4 release notes list 22 vulnerabilities. Most are stored cross-site scripting bugs that need a logged-in Contributor, Author or Editor account. The one that matters for every site is "a race condition during core updates that could lead to remote code execution", reported by Umut Bayram.
In plain terms: during a core update, WordPress unpacks the new version into a folder inside wp-content/upgrade/ before copying it into place. Patchstack's analysis explains that before 7.1.4 the folder's name was predictable, and the unpacked copy includes WordPress's setup script, which runs without your site's configuration. An attacker who requests that script during the few seconds the update takes can reach code execution. No login is needed. The attacker only has to catch the window while an update runs, and the folder has to be reachable from the web, which it is on many servers.
WordPress 7.1.4 adds 16 random characters to the folder name, keeps a blank index.php in the upgrade folder so it can't be listed, and stops a staged wp-config.php from being copied over. The severity ratings differ:
- Wordfence, which assigned the CVE, scores it 8.1 out of 10 (High), with high attack complexity because of the timing.
- WordPress's own security advisory rates it Low.
- CISA added it to its Known Exploited Vulnerabilities catalog on 3 November 2026 and gave US federal agencies until 6 November to fix it.
Attackers didn't wait. SecurityWeek reported Wordfence's figures: more than 18,500 requests aimed at the staged setup script in the first 21 hours after Wordfence deployed its firewall rule. Cyber Security News later reported more than 240,000 attempts from 28 October, with a peak of over 74,000 on 30 October. These are blocked requests, not confirmed break-ins, but they show bots are polling sites in case one starts updating.
The release also updates the root certificates WordPress bundles for its own outgoing HTTPS connections, after the eMudhra revocation. If your own site uses an emSign certificate, our post on the eMudhra emSign distrust explains what to do.
Is my WordPress site affected? Fixed versions by branch
WordPress backported the fixes to every branch down to 4.7, so you can patch without jumping to 7.1 straight away. From the release notes:
| Your branch | Update to at least | Of the 22 issues, affected by |
|---|---|---|
| 7.1 | 7.1.4 | All 22 |
| 7.0 | 7.0.8 | All 22 |
| 6.9 | 6.9.11 | All 22 |
| 6.8 | 6.8.12 | 20 |
| 6.7 | 6.7.11 | 20 |
| 6.6 | 6.6.11 | 19 |
| 6.5 / 6.4 | 6.5.14 / 6.4.14 | 17 |
| 6.0 to 6.3 | 6.3.14, 6.2.15, 6.1.16, 6.0.18 | 9 |
| 5.9 | 5.9.20 | 9 |
| 5.0 to 5.8 | The latest release in your branch (5.8.19 down to 5.0.31) | 6 |
| 4.7 to 4.9 | 4.9.35, 4.8.34, 4.7.39 | 4 or 2 |
| 4.6 and older | No fix: upgrade to a supported version | Not covered |
WordPress also reminds everyone that "only the most recent version of WordPress is actively supported". The backports are a courtesy, so plan the move to 7.1.
How to check your WordPress version
- Dashboard: the At a Glance box and the bottom-right corner of every admin page show the version number.
- Site Health: go to Tools, Site Health, Info, and open the WordPress section. The same screen's Server section shows your PHP version.
- WP-CLI, if you have SSH access:
wp core version # prints e.g. 7.1.4 wp core check-update # lists newer releases, if any
WordPress applies security releases automatically on sites that allow background updates, and the 7.1.4 announcement says those updates start on their own. Don't assume yours did: check the number.
How to update to WordPress 7.1.4 safely
- Take a full backup of files and database, and confirm you know how to restore it.
- Block
/wp-content/upgrade/first if your server lets you (next section). The update to 7.1.4 is unpacked by your current, unpatched code, so the window exists one last time while it runs. - Update: go to Dashboard, Updates and click the update button. With WP-CLI:
wp core update # newest version, 7.1.4 wp core update --minor # newest release in your branch, e.g. 6.8.12 wp core update-db # finish any database update wp core version - Update plugins and themes as well, then clear your page cache. Our guide to speeding up WordPress covers caching if it's new to you.
- Check PHP. A patched WordPress on an unpatched PHP is still exposed. See which PHP version to use for WordPress, including the October 2026 PHP fixes.
How to block web access to /wp-content/upgrade/
Patchstack's advice to hosts is to deny web access to wp-content/upgrade/ and make sure it can't be listed. A security plugin can't do this, because the unpacked copy never loads your site or its plugins: the block has to sit in the web server. Updates still work afterwards, because WordPress reads and writes this folder directly on the server, never through the web.
Apache or LiteSpeed (.htaccess)
Add this to the .htaccess file in the folder that contains wp-content, above the # BEGIN WordPress block:
# Block web access to the WordPress update folder (CVE-2026-119977)
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule ^wp-content/upgrade/ - [F,L]
</IfModule>
Don't put a separate .htaccess inside the upgrade folder itself: WordPress empties that folder before every update, apart from its index.php.
nginx (VPS)
Add this inside your site's server block:
location ^~ /wp-content/upgrade/ {
deny all;
}
The ^~ matters. Without it, nginx checks regex locations such as your location ~ \.php$ block first, and PHP files in the folder would still run. Then test and reload:
sudo nginx -t && sudo systemctl reload nginx
curl -I https://yourdomain.in/wp-content/upgrade/index.php # should return 403 Forbidden
HostEthical web hosting runs nginx, so a .htaccess rule has no effect there. The fix that matters is updating to 7.1.4 or your branch's backport, which closes the hole whether or not the folder is blocked. On shared hosting elsewhere, ask your host whether it blocks the folder server-wide.
How to check if your WordPress site was hacked
If your site was still on an affected version after 28 October 2026, check it. You need SSH or your host's file manager. Run the commands from the folder that contains wp-content.
- Admin accounts you don't recognise. Look at the registration dates too:
Without WP-CLI, open Users, All Users and filter by Administrator.wp user list --role=administrator --fields=ID,user_login,user_email,user_registered - PHP files changed since 28 October. Updates change files too, so compare the list with what you updated. Anything in
wp-content/uploads,wp-content/mu-pluginsor the root folder deserves a close look:find . -type f -name '*.php' -newermt '2026-10-28' -not -path './wp-content/cache/*' | sort - PHP files in uploads. That folder should hold images and documents. A blank
index.phpleft by a plugin is normal; anything else needs checking:find wp-content/uploads -type f -name '*.php' - Core files that don't match WordPress.org. This checks every core file against the official checksums and lists any that were modified:
The plugin check uses WordPress.org's checksums, so premium plugins bought elsewhere are not covered.wp core verify-checksums wp plugin verify-checksums --all - Plugins you didn't install. Run
wp plugin listandwp plugin list --status=must-use. Must-use plugins load automatically and are easy to miss in the admin screen. - Requests to the upgrade folder in your access log. Attackers request the staged
setup-config.php. Successful (200) responses here are the ones to worry about:grep -E "wp-content/upgrade/.*\.php" access.log
If you find something, restore a backup from before the first suspicious change, then immediately block the folder and update WordPress, because the restored copy is the old, vulnerable version. Delete unknown admin accounts. Change the passwords for every admin, the database and your hosting or SFTP login, and put new security keys in wp-config.php from the WordPress.org key generator. If you can't tell what was changed, get a professional clean-up before putting the site back online. Our guide to WordPress hosting in India lists what to look for in backups when choosing a host.
Elementor Pro CVE-2026-32475: check this too
A separate flaw in the paid Elementor Pro plugin is also being exploited. CVE-2026-32475 lets an attacker with no account upload a PHP file through a form's File Upload field and then run it. It affects Elementor Pro 4.2.1 and older and was fixed in 4.2.2 on 19 August 2026. SecurityWeek reported that attacks began right after the fix shipped and that Wordfence had blocked more than 190,000 attempts by early September.
Elementor told BleepingComputer that only sites with a published form whose upload field has multiple file uploads switched on (off by default) are at real risk, but it still recommends that every site update. To check:
wp plugin get elementor-pro --field=version
find wp-content/uploads/elementor/forms -type f -name '*.php'
That folder stores form uploads, so any .php file in it is a strong sign of compromise, according to BleepingComputer's report on the attacks. Updating the plugin doesn't remove files uploaded before you updated, so check even if you're already on 4.2.2.
Frequently asked questions
What is CVE-2026-119977 in WordPress?
It is a race condition in the WordPress core update process. During an update, WordPress unpacked the new files into a predictable folder under wp-content/upgrade, and an attacker without an account who requested the setup script in those few seconds could run code on the server. WordPress 7.1.4 fixed it on 28 October 2026, and CISA listed it as actively exploited on 3 November 2026.
How do I check which WordPress version I have?
Log in to the dashboard and look at the At a Glance box, or the version number at the bottom right of any admin page. Tools, Site Health, Info also shows it under the WordPress section, and your PHP version under Server. With SSH access, the WP-CLI command wp core version prints it. You are protected from CVE-2026-119977 on 7.1.4, 7.0.8, 6.9.11, 6.8.12 or the latest release of an older branch back to 4.7.39.
Will WordPress update to 7.1.4 automatically?
Usually, yes. WordPress installs security releases automatically on sites that allow background updates, which is the default, and the 7.1.4 announcement says those updates start on their own. Some hosts, plugins or wp-config.php settings turn this off, and a background update only runs when the site gets visits. Check the version number yourself, and update by hand from Dashboard, Updates if it is still below 7.1.4.
How can I tell if my WordPress site was hacked through this flaw?
Look for administrator accounts you did not create, PHP files changed since 28 October 2026 that you cannot explain, and PHP files inside wp-content/uploads. Run wp core verify-checksums to find modified core files, list plugins including must-use plugins, and search your access log for requests to PHP files under wp-content/upgrade. If anything looks wrong, restore a clean backup, update at once and change every password.
Does blocking wp-content/upgrade stop WordPress updates from working?
No. WordPress reads and writes the upgrade folder directly on the server during an update, never through the web, so denying web access to it only stops outside visitors and bots. On Apache or LiteSpeed you can add a rewrite rule to the main .htaccess file, and on nginx a location block with deny all. The block adds protection, but updating to 7.1.4 is the actual fix.