By Greg Nowak. Updated November 6, 2026.
A WordPress emergency update announcement should trigger a check across every site you own or maintain. Automatic delivery helps, but it cannot tell you whether an overlooked campaign site, a client installation or an old staging copy actually received the patch.
For business owners and agency teams, the useful outcome is a short, evidenced list: which sites are current, which still need attention, whether essential functions work, and who owns each unresolved problem. Here is how to get there.
What WordPress forced—and what it could not guarantee
The July 17 security announcement enabled forced updates for affected versions through WordPress’s automatic update system. It also made the limitation clear: automatic delivery depended on sites supporting background updates.
That release fixed SQL injection and a REST API batch-route issue that could lead to remote code execution. The July fixes were WordPress 7.0.2, 6.9.5 and 6.8.6, with the 6.8 branch affected only by the first issue. Versions before 6.8 were unaffected by those particular vulnerabilities; that does not establish their overall security.
An update notification is therefore a useful starting point. Confirming the installed version is what closes the delivery question.
The July patch is no longer the target
As of November 6, 2026, the official release archive lists WordPress 7.1.4, released October 28, as the latest stable release. The 7.1.4 announcement describes further security fixes, including an upgrade-process weakness that could allow remote code execution during the upgrade window.
Plan for the latest stable release. If an integration temporarily blocks that move, confirm the newest available security patch for the installed branch and give the full upgrade an owner and deadline. WordPress describes older-branch backports as a courtesy; they are not continuing active support.
Use a status that leads to an action
| Finding | Next action | Evidence to keep |
|---|---|---|
| Installation not checked | Verify directly or obtain access | Hostname, path and responsible person |
| Security updates missing | Patch promptly and assess exposure | Previous version and update history |
| Update blocked | Resolve the blocker and set a deadline | Error, dependency and assigned owner |
| Unexpected files or accounts | Preserve evidence and investigate | Files, logs and account details |
| Current and tested | Close the maintenance task | Version, check time and test results |
How to check every WordPress installation
1. Reconcile the site list
Compare your register with hosting accounts, domain records, deployment repositories and maintenance agreements. Include staging copies, regional sites, campaign sites and old migrations that remain accessible. Decide whether each installation should be maintained, restricted or retired.
Record its hostname, installation path, environment, host, business owner and technical owner. Where a client, agency and hosting provider share responsibility, name the person coordinating completion. Shared responsibility still needs one clear point of contact.
2. Read the installed version
With WP-CLI available, run these commands from the correct installation directory:
wp core version
wp core check-updateSave the output and verification time against that installation. Without shell access, use Dashboard → Updates and ask the host or maintainer to confirm the deployed version. Leave inaccessible sites marked unresolved.
3. Update through the site's maintenance process
Confirm that you have a usable backup of files and database, plus a recovery route. Check critical integrations on staging where feasible. If suspicious changes are already visible, preserve relevant evidence before overwriting files.
For installations maintained directly with WP-CLI, the core update command targets the latest version by default:
wp core update
wp core versionFor repository deployments or managed hosting, use the established deployment process so the next deployment retains the patch. Ask the maintainer to investigate failed automatic updates using the recorded error, Site Health, update configuration, file ownership and permissions. A manual patch solves the immediate gap; the failure also needs an explanation.
4. Check core file integrity
Compare core files with WordPress.org’s published checksums:
wp core verify-checksums --include-root --version=$(wp core version)The checksum command avoids loading WordPress during verification. Supply the correct --locale when checking a localized package. Retain the output and exit status. The documentation currently marks --format as unavailable in a stable WP-CLI release, so do not assume JSON output is supported by your installed tooling.
Investigate mismatches rather than dismissing them. The --include-root option also warns about non-WordPress items in the root directory, which can be legitimate. A clean result covers core files; it does not clear plugins, themes, uploads, configuration, accounts or the database.
5. Test what earns revenue or saves work
Choose checks that reflect the site’s purpose: submit a form and confirm delivery, complete an approved checkout test through payment confirmation, or publish content and check the public page. Include relevant logins, CRM connections and scheduled tasks.
Record the tester, result and any follow-up owner. A working homepage is too narrow a test for a site that handles enquiries or orders.
When should you investigate possible compromise?
A vulnerable version does not prove compromise, and patching does not remove an existing compromise. Establish the exposure period as far as records allow, including whether the installation was publicly reachable.
Unfamiliar administrator accounts, unexplained file changes, suspicious requests or altered scheduled tasks warrant investigation. Preserve logs and files before cleanup. Missing logs leave uncertainty; they cannot demonstrate that nothing happened.
Make the next emergency easier to manage
Keep the register current and agree who monitors releases, verifies installations, tests business functions and follows up exceptions. Each emergency should end with evidence and assigned actions.
If responsibilities are scattered across hosting providers and agencies, Greg can help turn them into a workable maintenance process. Discuss your WordPress sites with Greg to establish what is covered, what remains unresolved and what should happen next.
Related on GrN.dk
- WordPress Plugin Updates: What the Six-Hour Cooldown Can’t Check
- WordPress Security Updates Need an Ops Runbook
- Apache 2.4.68: What to Check Before You Call It Patched
Need help with this kind of work?
Discuss your WordPress sites with Greg Get in touch with Greg.