WordPress 7.1.4: the update flaw attackers are already probing
On 28 October WordPress released version 7.1.4, a security release that fixes 22 vulnerabilities. The worst lets an attacker run code on your server without an account, while WordPress installs a core update.
Attackers began probing for it within hours. Most sites update themselves, but you should check yours today.
What WordPress fixed
WordPress published 7.1.4 on 28 October 2026 and told site owners to update straight away (WordPress.org). The release notes count 22 vulnerabilities (WordPress 7.1.4 release documentation).
Most of them need the attacker to have an account on your site already, at Contributor level or above. Two need no account at all:
- CVE-2026-119977: a weakness in the core update process that can let an attacker run code on your server. This is the serious one.
- Unpublished Customizer changes: a visitor could see design changes you had drafted but not yet published.
The release also updates the security certificates WordPress ships with, after the certificate authority eMudhra had a root certificate revoked (Pantheon).
How the update flaw works
When WordPress installs a full core update, versions 4.7 to 7.1.3 unpack the new files into a predictable folder inside wp-content/upgrade. That temporary copy includes the WordPress installer. On many servers anyone on the web can reach that folder, so an attacker who requests the installer at the right moment can use it to run PHP code (Wordfence).
The catch for attackers is timing. In Wordfence’s tests the folder existed for a few seconds before WordPress cleaned it up, so a single request seldom lands. Automated tools that keep asking can still win the race. Wordfence rates the flaw 8.1 out of 10 on the CVSS severity scale and credits researcher Umut Bayram with finding it.
The risky moment is the update itself. Updating to 7.1.4 opens the window one last time, and the fixed version closes it for good. WordPress 7.1.4 gives the folder a random name and adds guards so the staged copy cannot run.
Is anyone using it?
Wordfence says attackers are trying. Its new firewall rule caught its first attack attempt nine minutes after going live on 28 October. In the first 21 hours Wordfence logged more than 18,500 requests aimed at the staged installer, and two of the busiest sources kept polling the same small groups of sites for about 14.5 hours (Wordfence).
Those figures count attempts. As of 2 November we have found no confirmed report of a site taken over through this flaw. Pantheon, a managed WordPress host, has put its own protections in place across its platform and still asks customers to update.
Which WordPress versions are safe
Version 7.1.4, or anything newer, closes the flaw. WordPress also released fixes for older branches, back to 4.7. If your site runs an older branch, these are the versions to look for:
- 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
- 6.3: 6.3.14 · 6.2: 6.2.15 · 6.1: 6.1.16 · 6.0: 6.0.18
- 5.x: 5.9.20, 5.8.19, 5.7.21, 5.6.23, 5.5.24, 5.4.25, 5.3.27, 5.2.30, 5.1.28, 5.0.31
- 4.x: 4.9.35, 4.8.34, 4.7.39
WordPress lists these on its 7.1.4 release page and calls the older-branch fixes a courtesy: it supports the latest version alone. WordPress 4.6 and older get no fix at all.
What to do today
- Check your version. Log in to WordPress and open Dashboard > Updates. It shows the version you run and whether a newer one is waiting.
- Update if you are behind. Click Update Now. Sites with automatic background updates should have started on their own, but Wordfence advises checking rather than assuming it worked (Wordfence).
- On an old branch, plan a move to 7.1. The older-branch fixes protect you for now, but WordPress supports the latest version alone. Test the upgrade on a staging copy first if your host offers one.
- Ask your host or developer about the upgrade folder. A server rule that blocks web access to
wp-content/upgradeduring the update shuts the window. Wordfence agreed in a reply to a reader that this is the best course for anyone who can do it. If you cannot, update anyway: waiting leaves all 22 flaws open. - Do not lean on a firewall plugin alone. Wordfence’s paid plans got a blocking rule on 28 October. Free users get it on 27 November, after Wordfence’s usual 30-day delay. Wordfence says the rule does not replace the update.
Signs to look for
If your site stayed unpatched for a few days, Wordfence suggests checking for (Wordfence):
- requests to PHP files inside
wp-content/upgradein your server logs - administrator accounts you do not recognise
- plugins you did not install, or PHP files you did not put there
Any of these needs a closer look. Our guide on how to check if your WordPress site is hacked covers the other signs, and what to do if your website is hacked covers the clean-up.
Can a scan tell if you are vulnerable?
An outside scan can see your WordPress version when your site publishes it, and not otherwise. Many sites do, in a generator tag in the page code or in the default readme file.
Where your site shows its version, our free check compares it with the latest WordPress release and flags an out-of-date install. It cannot see your version when you hide it, and it cannot tell whether someone has already broken in. Hiding version details is worth doing anyway: see how to hide your server version. Your Dashboard > Updates screen gives the reliable answer.
Open Dashboard > Updates today. If it does not say 7.1.4, or the fixed release for your branch, update now.
Common questions
What is CVE-2026-119977?
Has my site updated itself?
Is it safe to update when the flaw sits in the update process?
Does Wordfence Free protect me?
I run an older WordPress version. Is there a fix?
Sources
- WordPress 7.1.4 release announcement · WordPress.org, 28 October 2026
- Version 7.1.4 release documentation · WordPress.org, 28 October 2026
- WordPress 7.1.4 patches unauthenticated upgrade-window RCE · Wordfence, 29 October 2026
- WordPress 7.1.4 release notes · Pantheon, 28 October 2026