Guide · Breaches
Stop assuming WordPress updated itself: check for 7.1.4
On October 28, 2026, WordPress released version 7.1.4 with fixes for 22 security issues. The most serious one can let a stranger run code on your site during the few seconds it is installing a core update, and attackers started probing for it within hours. Most sites update on their own. Don’t assume yours did.
In under a minute:
- Log in and open Dashboard › Updates. You want WordPress 7.1.4, or the patched release for your branch (for example 7.0.8 or 6.9.11).
- Still on 7.1.3 or older? Update now, or ask your host or web person to do it today.
- If it sat unpatched, ask them to look for admin accounts, plugins or files nobody recognizes.
Make “is the website patched?” a monthly habit, not a guess. The Small Business Security Essentials Toolkit ($79) includes an Asset & Admin Inventory to record what runs your site and who has admin, and a Security Calendar & Renewals sheet to schedule the monthly update check.
What happened
WordPress 7.1.4 shipped on October 28, 2026 as a security release, and WordPress recommends updating immediately. Among the fixes is “a race condition during core updates that could lead to remote code execution.” According to the WordPress security advisory, during a full-package core update WordPress unpacked the new files into a predictable folder inside the web-served upgrade directory. An attacker with no account who hits that folder at exactly the right moment could get code running on the server. The fix was backported to every branch back to 4.7.
Wordfence, which shipped a firewall rule for paying customers about three hours after the release, says the first matching attack request arrived nine minutes after that rule went out, and it recorded more than 18,500 requests aimed at the staged installer files in the first 21 hours (SecurityWeek, Oct 30, 2026). The attack is hard to pull off, because it needs a very narrow timing window, and Wordfence has not reported a successful break-in. Attackers repeatedly polled some sites for hours to try to catch that window. See it on our Recent breaches page.
Check your version in two minutes
- Log in to your site’s admin area (usually yoursite.com/wp-admin).
- Go to Dashboard › Updates. The page shows your current version.
- On 7.1.4 (or the patched release for your branch)? You’re done. Not on it? Update, or ask whoever manages the site to update it today.
- Can’t log in, or someone else runs the site? Email your host or web person and ask: “Is our WordPress on 7.1.4 or the patched release for our branch?”
If it wasn’t updated
- Update first, then ask your host or web person to check for administrator accounts nobody recognizes, plugins nobody installed, and stray PHP files under wp-content/upgrade.
- Ask whether the web server blocks public access to the wp-content/upgrade folder. The attack requests a staged file directly, without loading WordPress, so an ordinary security plugin may never see it. Wordfence says its users need the firewall’s Extended Protection mode for its rule to apply.
- Make sure you have a recent backup stored somewhere other than the web server. See our backup guide.
If you run a team
- Put one name next to the website. Whoever it is checks the WordPress version, plugins and backups every month.
- Keep automatic updates on, but treat them as a convenience, not proof. Our automatic updates guide covers what to turn on.
- Know who has admin. Remove old admin accounts for past staff and contractors.
Bottom line
Automatic updates handle most WordPress sites, but “most” isn’t “yours.” Spend two minutes on Dashboard › Updates and confirm 7.1.4 (or your branch’s patched release). If it didn’t happen, update today and have someone check for anything new that nobody added.
Prefer video? Watch the under-a-minute version on YouTube: STOP Assuming Your WordPress Site Updated Itself.
Free next step: Get the Small Business Cybersecurity Checklist — download it now, or sign up there to get it by email and hear about new guides.