WordPress 7.1.4 fixes 22 security issues, including one that strikes during updates
Published · Disclosed October 28, 2026 · By Adam Taylor
WordPress released version 7.1.4 on October 28. It’s a security release, and a big one: WordPress counts 22 vulnerabilities fixed in it, more than three times the seven fixed in 7.1.3 at the start of the month.
One of them stands out, and it’s an unusual one: it needs no login, and it can only happen while your site is updating.
Am I affected?
If your site runs any version of WordPress older than 7.1.4, yes.
To check, log in and look at Dashboard → Updates, or at the version number in the bottom right of the dashboard home screen.
Most sites will already have updated themselves. WordPress installs security releases like this automatically unless that’s been turned off, or your host manages updates for you. Automatic doesn’t mean instant, though, and plenty of sites have it switched off without the owner knowing. It takes ten seconds to check.
If you skipped 7.1.3, 7.1.4 includes those fixes too.
The one that matters: a gap during updates
When WordPress updates itself, a plugin, or a theme, it first unpacks the new files into a working folder, wp-content/upgrade/, and copies them into place. That takes a few seconds.
Until 7.1.4, that folder’s name could be predicted, and on many servers it could be opened from the web while the update ran. The unpacked copy includes WordPress’s own setup screen. An attacker who reaches it at the right moment can run that setup against a database they control, without logging in, and use it to run code on your server.
It’s hard to pull off. The attacker has to hit a window of a few seconds, and only while an update is running. Patchstack, which wrote up the details, says it wouldn’t call it practical to exploit. But the window opens on every update, including the automatic ones nobody is watching, so it was worth closing.
7.1.4 closes it by giving the folder a random name and keeping a file in it that stops its contents being listed. We haven’t seen any confirmed reports of a site being broken into this way.
The other 21
Most are stored cross-site scripting: ways to save a script in your site’s content that then runs in the browser of whoever views it. They turn up in several blocks (Categories, Playlist, image, and comment page links), the Customizer, privacy data removal requests, specially crafted usernames, and the Interactivity API that newer blocks use.
The rest include a way to crash pages through the Interactivity API, unpublished Customizer changes that a logged-out visitor could find, and notes on a post that some users could read without being allowed to edit that post. WordPress also updated its bundled security certificates after certificates from one provider, eMudhra, were revoked.
What to do
- Update to 7.1.4. Dashboard → Updates → Update Now. Take a backup first if your site is heavily customised.
- On an older version you can’t move off yet? The fixes have been backported to every branch back to 4.7, so update to the latest release in your branch: 7.0.8, 6.9.11, 6.8.12, 6.7.11, 6.6.11, 6.5.14, 6.4.14, and so on down to 4.7.39. Sites on WordPress 4.6 or older get no fixes at all.
- Check that automatic updates are on, so the next one isn’t up to you.
- If you can’t update right away, ask your host to block web access to the
wp-content/upgrade/folder. That’s what Patchstack recommends as a stopgap. It’s a server setting, not something you change in WordPress.
On a Protect plan? Core updates are part of what we do, so this is already handled and you don’t need to act.
Not sure your site updated, or worried something already got in? Ask us and we’ll take a look.