WordPress 7.1.4 Security Flaw: Fix CVE-2026-119977 Safely
Updating WordPress is supposed to make your website safer. But a serious flaw in WordPress itself turned the update process into a risk: during an update, an attacker could run code on your server without even logging in.
This flaw is tracked as CVE-2026-119977. It is already being exploited in real attacks, and it affects a very wide range of WordPress versions. A fix exists — but the order matters. Clicking “Update” on an affected site without preparation passes through the exact window attackers target. Below is the problem in plain English, and the safe fix.
Watch the Video
Watch the video version of this security alert:
Who Is Affected
This flaw affects WordPress versions 4.7 through 7.1.3 — many years of WordPress releases. If your site runs any version in that range and has not yet been patched, it is affected.
The flaw is in WordPress core, the main WordPress software itself, not one single plugin or theme. Any site running an affected core version can be at risk during a full-package update.
WordPress fixed it in version 7.1.4, released October 28, 2026, with patched releases for other supported branches too. If your site is on an older branch, use your branch’s patched release — the goal is the same.
CISA, the United States cybersecurity agency, added CVE-2026-119977 to its Known Exploited Vulnerabilities list on November 3, 2026, confirming active exploitation. Wordfence recorded more than 18,500 requests aimed at staged installer paths in the first 21 hours. Those were attack attempts, not confirmed breaches — but they show how fast attackers began scanning.
How the Attack Works
During a full-package update, WordPress downloads the new version and unpacks it in a temporary staging folder: wp-content/upgrade/. Only then does it move the new files into place.
The problem has two parts:
- The staging paths were predictable and reachable from the web, so an attacker could guess where staged files would appear and request them directly.
- There was a race condition. A race condition means two things happen at the same time, and the result depends on which finishes first. During the update there was a short window when staged files were in place but the update had not finished. An attacker who reached the staged files inside that window could run code on the server.
No login was needed. Running code on your server can give an attacker control over your website — which is why the fix must close this window before the update starts. (We omit exploit details deliberately; site owners need the fix, not the attack recipe.)
The Fix, Step by Step
Do these steps in this exact order. Do not skip ahead to the update.
Step 1: Back up your site
Make a full backup — all files and the database — and store a copy outside the website itself, for example by downloading it. If anything goes wrong, you can restore your site.
Step 2: Block web access to wp-content/upgrade/ BEFORE updating
This is the step most people miss, and the most important one.
Before you run the update, block web access to the wp-content/upgrade/ folder on your server. Then test it: try opening that folder address in a browser. The server must answer with a “403 Forbidden” error. That 403 response is the proof the block is working. If the folder still loads or shows a file listing, the block is not in place yet — do not start the update until you see the 403.
How you set this up depends on your hosting — many control panels can protect a folder, or a server rule can deny web access to that directory. If unsure, ask your hosting provider or a WordPress professional. Leave the protection in place afterwards: it blocks web visitors, not WordPress itself.
Step 3: Update to WordPress 7.1.4
Update to WordPress 7.1.4, or your branch’s patched release, from Dashboard → Updates. With the staging folder blocked, the update runs without exposing the window attackers target.
Step 4: Verify everything worked
After the update finishes, check three things:
- Your WordPress version. In your dashboard, confirm it shows 7.1.4 or your branch’s patched release.
- Your website loads normally. Visit your homepage and a few key pages, and check that contact forms and main features still work.
- The upgrade folder. Check wp-content/upgrade/ for unexpected PHP files. After an update this folder is normally empty; unexpected files are a warning sign — get help quickly.
How to Check If Your Site Is Affected
Ask yourself three questions:
- What WordPress version are you running? Find it on the Updates screen or at the bottom of most admin pages. Versions 4.7 to 7.1.3 are affected unless already patched.
- Did you update between October 28 and early November 2026 without blocking the upgrade folder? If so, your site passed through the risky window during that update. Check the wp-content/upgrade/ folder for unexpected PHP files.
- Is there anything unexpected in the upgrade folder right now? Open it through your hosting file manager or FTP. Files you do not recognise, especially PHP files left behind after an update, deserve professional attention.
If you find something unexplained, do not delete files at random — you could break the site or destroy evidence. Get a WordPress professional to check it properly.
Frequently Asked Questions
I already updated to WordPress 7.1.4. Am I safe?
On 7.1.4 or a patched branch release, the flaw is fixed. But if you updated between October 28 and early November 2026 without blocking the wp-content/upgrade/ folder first, check that folder for unexpected PHP files. The patch fixes the flaw going forward; it does not undo anything that happened during an unprotected update.
My site is small and gets little traffic. Do I still need to act?
Yes. The Wordfence figures show attackers scanning broadly and automatically, not picking sites one by one. Small sites are scanned too, and updating in the safe order takes little time.
What if I cannot update right now?
Block web access to the wp-content/upgrade/ folder and make a backup first. That reduces the exposure, but it is not a replacement for the patch. Plan the update to a patched release as soon as you can, and keep the folder blocked in the meantime.
Is this a plugin or theme problem?
No — it is a WordPress core flaw. Still update plugins and themes too, as outdated ones are a common attack route. Fix core first, then everything else.
Need Help Securing Your WordPress Site?
Unsure which version you run, or finding the blocking step technical? We can help. Intellectual Era Solutions provides WordPress development, maintenance, security, and IT consulting for clients worldwide.
Contact us through our website, or email us at info@intellectualerasolutions.com, and tell us what version of WordPress you are running. We will check your site and help you update safely, in the right order. Do not put it off — the fix is simple when done properly, and every unpatched update is a risk you do not need to take.
Sources: WordPress 7.1.4 release (October 28, 2026); CISA Known Exploited Vulnerabilities list entry for CVE-2026-119977 (November 3, 2026); Wordfence request figures (18,500+ requests to staged installer paths in the first 21 hours). Affected versions: WordPress 4.7 through 7.1.3.