WordPress Has an Actively Exploited Core Bug. Updating Is Step Two, Not Step One
By Zachary, Hawthorn Security
If your website runs on WordPress, and plenty of UK small business sites do, this one is for you. A flaw in WordPress core itself (not a dodgy plugin, for once) is now being used in real attacks. It has a quirk that makes the usual “just click update” advice slightly wrong.
It's not cause for panic, but it's worth 20 minutes of your time this week.
What happened
On 28 October WordPress released version 7.1.4, which fixed 22 security problems. Most were fairly minor. One wasn't: a race condition in the core updater, reported by researcher Umut Bayram of Picus Security, that can lead to remote code execution. That means an attacker could run their own code on your web server without logging in.
On 3 November the US Cybersecurity and Infrastructure Security Agency (CISA) added the flaw, tracked as CVE-2026-119977, to its Known Exploited Vulnerabilities list. That list only covers bugs with evidence of real attacks, so this has moved beyond theory.
How it works, in plain English
When WordPress updates itself, it briefly unpacks a temporary copy of its installer into a folder called wp-content/upgrade/. On many servers that folder can be reached from the web, and PHP code inside it will run.
If an attacker finds that temporary installer before WordPress tidies it away, they can point it at a database they control. The updater then writes a new wp-config.php (the file that holds your site's database details) over your real one. From there they can get an admin account, install a plugin of their choice and run whatever code they like.
It needs a few things to go the attacker's way: good timing, a server that runs PHP in that folder, and knowing where the temporary copy lives. So it's not trivial. It has been exploited anyway, and the underlying behaviour reportedly goes back to WordPress 2.7 in 2008.
Who's affected
- Public advisories list WordPress 4.7 to 7.1.3 as vulnerable.
- Fixed versions: 7.1.4, plus backported fixes for older branches, including 7.0.8, 6.9.11, 6.8.12 and so on down to 4.7.39.
- WordPress 4.6 and older get no fix at all. WordPress only properly supports its latest version, so if you're on something ancient, moving up is your only option.
A word of caution on the backports: not all of them carry all 22 fixes. Some of the older branches only got a handful. Being on “a patched version” of an old branch isn't the same as being on 7.1.4.
The traps people miss
The update is the risky moment. This is the unusual bit. The bug lives in the updater, so the act of updating can open the window an attacker needs. According to the researcher, updating can leave a web-reachable temporary installer behind on a site that hasn't been patched yet. Running wp core update from the command line doesn't get around it either, because it uses the same updater.
“Auto-updates are on, so I'm fine.” Maybe. Lots of sites have auto-updates on paper but stuck in practice, because of file permissions, a full disk or a host that disabled them. Check the version number yourself rather than assuming.
Patched doesn't mean clean. If your site was vulnerable and reachable over the past few weeks, updating now closes the door, but it won't evict anyone who already got in.
Forgotten sites. The old staging site, the campaign microsite from 2021, the “temporary” blog on a £5 VPS. These are the ones that never get updated and are easiest to find.
What you should do
- Block web access to
wp-content/upgrade/first. WordPress only uses that folder during updates, so visitors never need it. Ask your host to deny access (or at least PHP execution) there, or add a rule to your web server config. Then visit the folder in a browser and confirm you get a 403 “Forbidden” error. - Then update. Go to Dashboard > Updates and move to 7.1.4. If you're stuck on an older branch, at minimum get to its latest backport, and plan a move to the current version.
- Check the version number afterwards. Don't trust the auto-update setting. Look at the bottom of the admin dashboard or the Updates screen.
- Look for signs of trouble. Check for admin users you don't recognise, plugins you didn't install, and whether
wp-config.phphas changed recently. If anything looks off, assume the worst and get help. - Find every WordPress site you own. Make a list, including staging and old marketing sites. Update them or switch them off.
- Take a backup and test the restore. It's a good habit anyway. Keep a copy off the server, so a compromised site can't damage it.
If your site is on a managed WordPress host, much of this may already be handled. It's still worth a quick email asking them to confirm they've applied 7.1.4 and blocked the upgrade folder.
Not sure where you stand?
This is exactly the sort of thing I check in a Hawthorn Security review: which version of WordPress (and PHP, and everything underneath) you're actually running, whether your updates really work, whether folders that should be private can be reached from the web, and whether there's an old forgotten site somewhere on your server waiting to be found.
You get a plain-English report of what I found, ranked by what matters most, with clear steps to fix it. No jargon and no scare tactics.
Book a security review at hawthornsecurity.uk