
A flaw in the WordPress update system is being exploited and is fixed in 7.1.4. The first update can still expose the site: here are the affected versions and the safe procedure.
By Mouhamed BANKOLE, CEO at ITNET Technologies · Updated November 12, 2026 · Reading time: 10 min
On November 3, 2026, the US cybersecurity agency CISA added the WordPress vulnerability CVE-2026-119977 to its catalog of actively exploited vulnerabilities (CISA alert). The researcher who discovered it has since explained that the update fixing it can expose the site one last time while it installs, and recommends blocking a folder before updating (Picus Security analysis). If you run a WordPress site, here is what is confirmed, which versions are fixed, and how to update without taking any risk.
In short
- A WordPress core flaw in the update system is being exploited by attackers; it is fixed in WordPress 7.1.4 and in every maintained branch back to 4.7.
- The first update to the fixed version still runs the old code: for a few moments, the site can remain exposed.
- Before updating, block web access to the wp-content/upgrade folder and check that it returns a 403 error.
- On shared hosting, check with your host; on a VPS or dedicated server, the web server configuration is your responsibility.
- Versions 4.6 and earlier will not get a fix: you need to migrate to a maintained version.
Contents
- What happened with WordPress?
- Which WordPress versions are affected?
- Why can the update itself expose your site?
- What does this change for your website?
- How do you find your WordPress version?
- What should you do before running the update?
- How do you check that your site has not been compromised?
- Shared hosting or VPS: who has to run the update?
- What if your WordPress is too old to be fixed?
What happened with WordPress?
At the end of October 2026, WordPress fixed a flaw in its update tool that can let an unauthenticated attacker run code on the server, and this flaw is now being exploited.
What is confirmed, according to official sources:
- the WordPress team published its security advisory on October 29, 2026, with fixed versions for every branch from 4.7 to 7.1 (WordPress security advisory);
- the flaw was discovered by Umut Bayram, a researcher at Picus Security (WordPress security advisory);
- CISA added it to its catalog of exploited vulnerabilities on November 3, 2026 (CISA alert);
- the Canadian Centre for Cyber Security published an advisory the same day urging users to move to 7.1.4 (advisory AV26-1117).
One point is worth noting: the WordPress advisory rates the flaw as "low" severity, while the CVE record gives it a score of 8.1 out of 10, according to The Hacker News. For you, the conclusion is the same: the flaw is exploited and the update is a must.
Which WordPress versions are affected?
All WordPress versions released before the late-October 2026 fixes are affected; the reference version is now WordPress 7.1.4 (WordPress security advisory).
| WordPress branch | Affected versions | Fixed version |
|---|---|---|
| 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 to 4.7 | all versions before the branch fix | one fixed version per branch (for example 6.7.11 or 4.7.39) |
| 4.6 and earlier | all | no fix |
Sources: WordPress security advisory for affected and fixed versions, Picus Security analysis for versions without a fix.
Staying on your branch (for example moving from 6.8.11 to 6.8.12) fixes the flaw, but the latest branch remains the best choice to receive future fixes.
Why can the update itself expose your site?
Because the update to the fixed version is performed by the old, still vulnerable update tool: the fix only protects the updates that come after it (Picus Security analysis).
In simple terms:
- during an update, WordPress unpacks the new files into the wp-content/upgrade folder, which is reachable from the web on a typical install;
- the site stays exposed for a few moments, while the files are unpacked;
- once the fixed version is installed, later updates no longer carry this risk.
This is what emerges from the analysis published by The Hacker News on November 6: according to the outlet, attack attempts were observed as soon as firewall protections were rolled out (The Hacker News). We do not describe the attack method here: only the protective measures are useful to you.
What does this change for your website?
If your site is not yet on a fixed version, it is exposed to a server takeover, and the usual automatic update is not enough on its own to close the door safely.
Possible consequences, as analysis:
- defacement or redirection of the site to malicious pages;
- creation of hidden administrator accounts;
- theft of database content (customer accounts, orders, forms);
- use of the server to send spam or attack other sites.
Sites that update automatically may already have received the fixed version: check rather than assume.
How do you find your WordPress version?
Log in to the WordPress admin: the version is shown under Dashboard, then Updates, and at the bottom right of every admin page.
Other methods:
- on the Site Health page (Tools, then Site Health, Info tab);
- in the wp-includes/version.php file, on the $wp_version line, via FTP or the file manager;
- from the command line on a server:
wp core version.
If you manage several sites, list them all before you start, including staging sites and forgotten old installs: they are often the ones that get compromised.
What should you do before running the update?
First block web access to the wp-content/upgrade folder, check that it returns a 403 error, then run the update (Picus Security analysis).
The recommended procedure:
- take a full backup (files and database);
- block the folder in the web server configuration (examples below);
- test it: the address yoursite.com/wp-content/upgrade/ must return 403;
- update WordPress to 7.1.4 or the fixed version of your branch;
- check the displayed version and that the site works properly.
Blocking examples, to adapt to your server:
- nginx:
location ^~ /wp-content/upgrade/ { deny all; }; - Apache, in the .htaccess file at the site root:
RedirectMatch 403 ^/wp-content/upgrade/; - do not put an .htaccess file inside the upgrade folder itself: the old updater deletes it before running.
Another option is a manual update, replacing the core files from an archive unpacked outside the public folder, without touching wp-config.php or wp-content. According to Picus Security, the WP-CLI wp core update command is not a substitute for this precaution (Picus Security analysis).
Pro tip: keep the blocking rule after the update. It does not get in WordPress's way and protects against possible future flaws of the same kind.
How do you check that your site has not been compromised?
Check administrator accounts, plugins and the contents of the wp-content/upgrade folder, and look in the server logs for unusual requests to that folder.
What to check:
- administrator accounts you do not recognize;
- plugins installed without your approval;
- PHP files left in wp-content/upgrade after the update;
- requests to PHP files in that folder in the access logs;
- a site suddenly showing the WordPress installation screen.
If in doubt, do not just delete the suspicious file: restore a clean earlier backup, change every password (admin, database, FTP) and regenerate the security keys in wp-config.php.
Shared hosting or VPS: who has to run the update?
On shared hosting, the web server configuration is the host's job and the WordPress update is usually yours; on a VPS or dedicated server, both are your responsibility.
| Hosting type | WordPress update | Blocking the upgrade folder |
|---|---|---|
| Shared hosting | You, unless you have a maintenance service | You via .htaccess, or the host at server level |
| VPS or dedicated server | You | You, in the nginx or Apache configuration |
| Managed services | The provider, depending on the contract | The provider, depending on the contract |
On Wayhost web hosting, the plan page lists a web application firewall, malware scanning and removal, manual and automatic backups, and SSH/WP-CLI access from the panel (checked on November 12, 2026): these tools help with the backup beforehand and the checks after the update. On a VPS or a dedicated server, it is up to you to add the blocking rule to the web server configuration.
To choose hosting suited to WordPress beyond this flaw, see our WordPress hosting guide.
What if your WordPress is too old to be fixed?
WordPress versions older than 4.7 get no fix at all: the only lasting protection is to migrate to a maintained version (Picus Security analysis).
Such a migration needs preparation:
- test on a copy of the site first, never directly in production;
- check compatibility of the theme and plugins, often abandoned on very old sites;
- update PHP too, because an old WordPress often runs on a PHP version that is itself vulnerable: see our article on the PHP vulnerability and PHP updates;
- in the meantime, block the wp-content/upgrade folder and avoid any unattended automatic update.
FAQ
Is my WordPress site affected by CVE-2026-119977?
Yes, if its version is older than 7.1.4 or the fix for its branch. Check the version under Dashboard, then Updates. A site already on a fixed version is no longer exposed during later updates.
Is the WordPress automatic update enough?
It installs the fix, but the first update to the fixed version still goes through the old tool. Block the wp-content/upgrade folder first to remove this risk. Then check that the displayed version is indeed fixed.
What does blocking wp-content/upgrade mean?
It is a web server rule that prevents anyone from reaching this folder from a browser. WordPress keeps using it internally for its updates. Test the rule: the folder's address must return a 403 error.
Should I update WordPress plugins too?
This flaw affects the WordPress core, not plugins. Still, use the opportunity to update themes and plugins after a backup. Outdated plugins remain a frequent cause of hacked sites.
Does my host handle the update?
It depends on your contract: on standard shared hosting, updating WordPress is usually your job. On a VPS or dedicated server, everything is your responsibility. A managed service plan may include these operations.
How can I tell if my site has been hacked?
Look for unknown administrator accounts, plugins you did not install and PHP files in wp-content/upgrade. Also review the server access logs. If in doubt, restore a clean backup and change every password.
What if I cannot update right away?
At least block access to the wp-content/upgrade folder and disable unattended automatic updates. Schedule the update as soon as possible, after a full backup. Keep an eye on administrator accounts in the meantime.
Key takeaways
- CVE-2026-119977 is being exploited and is fixed in WordPress 7.1.4 and the maintained branches.
- The first update to the fixed version can still expose the site for a few moments.
- Block wp-content/upgrade and check for a 403 response before updating.
- Check accounts, plugins and logs after the update.
- Versions 4.6 and earlier must be migrated, as there is no fix.
To host your WordPress sites with a built-in web application firewall, malware scanning and backups (checked on November 12, 2026), discover Wayhost web hosting.
Article written by Mouhamed BANKOLE, CEO at ITNET Technologies.