WordPress 7.1.4 fixes a flaw in the update process that attackers are probing for; HKCERT rates it High. How to check your version and update safely.
- Date
- Reading
- 5 min read
- Written by
- Nick Li
- Tags
- #Risk#Web#Engineering
Nearly half of the .hk websites that run on a content management system run on WordPress, according to W3Techs. If yours is one of them, there is a security release waiting for it, and this one is unusual: the weak spot is WordPress's own update process.
On 28 October, WordPress shipped version 7.1.4 as a security release. Its headline fix is a flaw the researcher who found it describes as present since WordPress 2.7, released in 2008. HKCERT rates it High Risk and says it is being exploited in the wild, and on 3 November the US agency CISA added it to its list of known exploited vulnerabilities.
The good news: checking takes two minutes, and the fix is already published for every WordPress branch back to 4.7. Our Patch Tracker shows the safe version for each branch.
What the flaw is
When WordPress updates itself, it unpacks the new version into a temporary folder under wp-content/upgrade/. In most versions that folder had a predictable name, and it was reachable from the internet. Inside it sits WordPress's installer, which doesn't know the site already exists. An attacker who requests that installer in the few seconds before clean-up can feed it their own database details, and from there take over the site. No password is needed. The weakness is tracked as CVE-2026-119977.
Only full core updates expose that installer; plugin and theme updates don't ship it. The window is short, which is why WordPress's own advisory labels the issue Low, while the CVE record, scored by the security firm Wordfence, puts it at 8.1 out of 10: hard to pull off, serious if it works. Attackers deal with the short window by hammering the folder non-stop and waiting for a site to update.
One more detail worth knowing: the researcher, Umut Bayram of Picus Security, writes that he found the flaw in about four hours with an AI model as his research partner. Finding old bugs is getting cheaper, on both sides.
Is anyone attacking it?
Yes, at scale, though attempts are not the same as break-ins. Wordfence, which runs a firewall on millions of WordPress sites, said its rule caught more than 18,500 attempts in the first 21 hours after the release, and on 4 November BleepingComputer quoted it blocking about 13,000 attempts a day. Wordfence also said the large numbers don't mean many sites were actually taken over, and as of this writing no confirmed compromise has been published. Attackers are probing for sites that are about to update; the flaw bites at that moment.
Check your version in two minutes
Log in to your WordPress dashboard. The At a Glance box on the home screen shows the version at the bottom, and Dashboard → Updates says if you have the latest. Then compare it with the WordPress row of our Patch Tracker, which lists the safe version for each branch and updates itself every hour.
Two things people get wrong here:
-
An older branch can be safe. WordPress backported this fix to 24 older releases, down to 4.7.39. A site on 7.0.8 or 6.9.11 is patched, even though it isn't on 7.1. What matters is the last number in your branch.
-
Below 4.7, there is no fix. WordPress 4.6 and older receive no security updates at all. Those sites need a migration, not an update.
Update the safe way
Here is the twist in this story. The fix in 7.1.4 protects every future update, but the first update from an unpatched version still runs the old updater once, so it passes through the vulnerable window one last time. Picus, Wordfence and the security firm Xint all point this out. The answer is to close the door before you walk through it:
- Block web access to the upgrade folder at the web server. Your developer or host does this in a minute:
# Apache: put this in the .htaccess at the root of the site (not inside the upgrade folder)
RedirectMatch 403 ^/wp-content/upgrade/
# Nginx: inside the server block
location ^~ /wp-content/upgrade/ { deny all; }
Then open yoursite.com/wp-content/upgrade/ in a browser and make sure you get a 403 "Forbidden" page.
-
Update from Dashboard → Updates, or let the background update run.
-
Confirm the version now shows 7.1.4, or the fixed version for your branch.
-
Have a look around. Any PHP files left under
wp-content/upgrade/, any admin user you don't recognise, any plugin you didn't install: treat them as a sign of trouble and ask for help.
If your site is on managed WordPress hosting, ask the host whether they applied 7.1.4 and whether they blocked the upgrade folder. Some did both for their customers; some only block.
Why your site may not have updated itself
Security releases install automatically on most sites, and WordPress emails the site owner when that happens: the subject line is "Your site has updated to WordPress 7.1.4". If no such email arrived and the dashboard still shows an older version, the automatic updater is probably switched off, and that is common. Hosts disable it in favour of their own tools, a developer may have turned it off with a setting in wp-config.php, a leftover .git folder blocks it, and wrong file permissions stop it quietly. Tools → Site Health will tell you: look for "Background updates are not working as expected". The official guide explains each cause.
If someone else looks after your site
Most small businesses in Hong Kong don't touch WordPress themselves. Three questions for your agency or freelancer, which should get answers within a day:
-
"Which WordPress version is our site on, and does it match the safe version for that branch?"
-
"Was the upgrade folder blocked before the update, and is the update done?"
-
"Are automatic security updates working, and who gets the email when they run?"
This is the fourth WordPress-related HKCERT warning rated High or above since late September. Updates are no longer a once-a-quarter chore; our Patch Tracker exists so you can check in a minute whenever a headline makes you wonder.
The one time your site is most exposed is while it's updating. Block the folder first, then update, then check.
If you'd like us to check your site, or to talk to your developer with you, let's talk.
