WordPress released version 7.1.4 on Oct 28, 2026. It fixes 22 security flaws, and one of them drew attackers almost right away. If your business website runs on WordPress, here's what happened and what to check.
The flaw in the update process
When WordPress updates itself, it unpacks the new files into a temporary folder before moving them into place. That folder had a predictable name, and for a few seconds during an update, a complete copy of WordPress, including its setup screen, sat at an address anyone on the internet could guess. An attacker who reached it at the right moment could run the setup against a database they control and take over the site. No login was needed.
The odds of hitting that window are low, and the security firm Patchstack rated the attack as hard to pull off. Attackers tried anyway. In the first 24 hours after the fix came out, Wordfence blocked 62,969 attempts to exploit it, mostly automated scripts checking sites over and over in case an update happened to be running.
The fix gives the temporary folder a random name and keeps its contents from being listed during updates.
The other 21 fixes
Most of the remaining flaws are cross-site scripting bugs that need a logged-in user with Contributor, Author or Editor access. Others let visitors see unpublished Customizer changes, let custom comment-moderator roles read and edit notes on posts they shouldn't, and could freeze a visitor's browser tab. None of them is an emergency on its own, but together they're a good reason to update.
What to check on your website
- Your WordPress version. Look at the Dashboard, or ask whoever manages your site. You want 7.1.4. Sites on older branches got their own fixes, including 7.0.8, 6.9.11 and 6.8.12, going back to 4.7.39. Versions older than 4.7 get no security fixes at all and need to be upgraded.
- Automatic updates. Sites with automatic background updates got 7.1.4 on their own. Some hosts and setups turn these off, so confirm yours are on.
- The upgrade folder. Your host or web developer can block web access to the wp-content/upgrade folder. That's the surest fix, and it protects you during future updates too. A security plugin that only loads with WordPress can't block this attack. If you use Wordfence, make sure its Extended Protection mode is turned on.
- Plugins and themes. Most WordPress security problems are found in plugins and themes, not in WordPress itself. Keep them updated, and remove the ones you don't use.
- Backups. Make sure there's a recent backup of the site stored somewhere other than the web server, and that someone has tested restoring it.
Why this keeps happening
Website attacks are mostly automated. Scripts scan huge numbers of sites looking for any that haven't updated yet, so a small business site is just as likely to be hit as a big one. The gap between a fix coming out and attackers using it is now measured in hours, which is why updates can't wait for a slow week.
How we help
We keep our clients' computers, servers and software patched on a schedule, and we can look at who manages your website and how it gets updated. If you're not sure whether your site is current, give us a call. Our cybersecurity services cover the details.