Security

Update the Same Day or Wait? A WordPress Update Policy for People Who Look After Many Sites

Security releases go out the same day, automatically, with proof. Feature releases get a staging copy first. Decision table, checks, rollback, 7.1.x examples.

Varun DubeyVarun Dubey
·14 min read
Timeline of WordPress security releases 7.1.1 to 7.1.4 under the headline Same day, or wait?

Update the same day for security releases, and let WordPress do it for you. WordPress core already installs minor and security releases on its own on most sites, so the real work is proving that it happened. Feature releases, whether a new WordPress version or a plugin with a redesigned screen, should be tried on a staging copy first and rolled out over days.

This guide is for people who look after more than one site: freelancers, small agencies and in-house site managers with 10, 50 or 200 installs. We checked every setting, command and release below on 15 November 2026 against the WordPress developer documentation, the official release posts and Patchstack. The current stable release is WordPress 7.1.4, published on 28 October 2026.

Should you update WordPress the same day or wait?

For a security release, do not wait. WordPress marks these releases itself: the 7.1.4 notes say “Because this is a security release, it is recommended that you update your sites immediately.” For a feature release, wait. A new major version or a plugin with new behaviour can break a layout or a checkout, and a few days of testing costs very little.

The reason for the split is what each release gives an attacker. A security release publishes the fix, and the fix shows where the hole was. People compare old and new files and build an attack from the difference. A feature release changes behaviour but does not hand anyone a map to a vulnerability, so patience is cheap there.

What does WordPress update automatically by default?

On most sites, minor core releases and translation files update by themselves. The WordPress advanced administration guide says “By default, automatic updates of WordPress are enabled on most sites” and that minor updates and translations install automatically. Sites on version 5.6 or later also get major core updates automatically, unless a version control checkout is detected. The same page calls disabling these updates “strongly discouraged”.

Here is what that means in practice for a release like 7.1.4. The third number in the version changed, so it is a minor release on the 7.1 branch. The 7.1.4 notes say it can be installed from Dashboard, Updates, and the 7.1.3 and 7.1.2 posts both say sites with automatic background updates will start the update on their own. We found no page that calls 7.1.x “minor” in those exact words, so this rests on the numbering rule and the documented examples.

Plugins and themes behave differently. They do not update unless someone turns auto-updates on, either per item in the admin or with a filter. Since WordPress 5.5 the Plugins and Themes screens show an “Enable auto-updates” link for each item, and that setting is stored per site.

What do the core auto-update constants do?

They are two constants in wp-config.php that override what the dashboard shows. The official documentation describes them like this:

Setting

Effect

Source note

WP_AUTO_UPDATE_CORE set to true

Development, minor and major core updates all enabled

Overrides the setting on the Updates screen

WP_AUTO_UPDATE_CORE set to 'minor'

Minor updates enabled, development and major updates disabled

The right value for sites that must not jump versions unattended

WP_AUTO_UPDATE_CORE set to false

All core automatic updates disabled

This blocks security releases too

AUTOMATIC_UPDATER_DISABLED set to true

Turns off all automatic updates, core or otherwise

Disabling is strongly discouraged

auto_update_plugin filter

Returning true enables auto-updates for all plugins, including ones installed later

Overrides every choice in the admin screen, and the screen does not show it

auto_update_theme filter

Same idea for themes

Same override behaviour

allow_minor_auto_core_updates and allow_major_auto_core_updates filters

Turn minor or major core updates on or off in code

Documented with __return_true examples

Checked on 15 November 2026 against the WordPress upgrade documentation and the WordPress 5.5 auto-updates developer note. A site with no constant set is not a mystery: it uses the defaults above. But a site with false or true in the wrong constant will silently ignore the security release, which is why we read the constants instead of trusting the dashboard.

Two more things can stop core from updating even when the settings allow it. A version control checkout (a .git or .svn folder above the site) makes WordPress assume you manage code yourself and skip automatic core updates. And a web server that cannot write to the files cannot apply an update at all.

How do plugin and theme auto-updates work?

Each plugin and theme has its own switch. In the admin it is the “Enable auto-updates” link on the Plugins and Themes screens. From the command line, WP-CLI has wp plugin auto-updates with enable, disable and status subcommands, and wp plugin list includes an auto_update column by default.

# Checked on 15 Nov 2026 against the WP-CLI command pages
wp plugin list --fields=name,version,update,auto_update --format=table
wp plugin auto-updates enable akismet
wp plugin auto-updates status akismet

To switch everything on in code, add the two filters to an mu-plugin. To keep a short list of risky plugins on the staged track, return false for those slugs and pass everything else through. The filter receives the current decision and the update item, and the item carries the plugin slug.

<?php
// wp-content/mu-plugins/update-policy.php  (checked on 15 Nov 2026)
add_filter( 'auto_update_theme', '__return_true' );

add_filter( 'auto_update_plugin', function ( $update, $item ) {
	// Plugins that handle money or logins stay on the staged track.
	$staged = array( 'woocommerce', 'memberpress' );
	if ( in_array( $item->slug, $staged, true ) ) {
		return false;
	}
	return true;
}, 10, 2 );

A filter like this overrides what each admin chose, and the admin screen will not reflect it. The WordPress developer note says to pair these filters with the interface hooks so people know which policy applies. We keep one policy file per site and name it in the site notes, so a colleague does not turn a switch off by hand and wonder why it came back.

The full setup for many sites, with inventory scripts and cron, is in our WP-CLI guide to auto-updates at fleet scale. This post is about the decision: which update goes on which track, and how you know it worked.

Does WordPress roll back a plugin update that breaks the site?

Sometimes, and only for one case. Since WordPress 6.6, a plugin that updates automatically is rolled back if the site shows a PHP fatal error afterwards. The core merge proposal describes the mechanism: WordPress makes a loopback request to the home page, and if that request hits a fatal error, “the previously installed version of the plugin is restored”. An email goes to the address in the admin_email option, and the next update check tries the plugin again. Maintenance mode stays on for the whole automatic update run. Source: the Rollback Auto-Update merge proposal.

Here is what that feature does not do:

  • It covers plugin auto-updates. The proposal does not describe theme or core auto-updates being rolled back.
  • It catches fatal errors on the home page. A broken checkout, a missing form or a layout problem is not a fatal error and is not caught.
  • It depends on loopback requests working. The proposal says a failed loopback is treated as a detected fatal error, so a site whose loopback is broken can see good updates reverted.
  • Manual updates have their own, older safety net: WordPress 6.3 added rollback for failed manual plugin and theme updates.

So the rollback is a seat belt, not a reason to skip backups. It narrows the damage from one kind of failure on one kind of update.

What do real security releases teach us about waiting?

Four WordPress core releases came out in about six weeks, and each one is a different lesson. The table lists them with the source for every claim. We deliberately use only facts from the release notes, the advisory data and Patchstack’s published analysis.

Release

Date (UTC)

What it fixed

What it shows

7.1.1

17 Sep 2026

Click2Shell, per Patchstack. An administrator must load a crafted URL while logged in; no CVE ID is given in that article.

Not every security release is equally urgent, but the fix is still the same action.

7.1.2

22 Sep 2026

CVE-2026-87902, rated critical in the release post. An unauthenticated attacker can make page-template resolution include a chosen readable local PHP file. CVE.org lists versions below 7.1.2 as affected.

Patchstack saw the first attack attempt on 22 Sep at 11:49 UTC, the same day as the release.

7.1.3

6 Oct 2026

Seven security fixes and four bug fixes, per the release post. They include a stored XSS on the Comments screen, a second-order SQL injection in the WXR export and an unauthenticated disclosure of comments on private posts.

A bundle of mid-severity fixes is why a blanket same-day rule beats triage.

7.1.4

28 Oct 2026

22 vulnerabilities in the release notes, including a race condition during core updates that could lead to remote code execution, and updated root certificates.

The updater itself can be a target, so automatic does not mean safe by itself.

7.1.2: the attack arrived with the patch

The release post is dated 22 September 2026 and names CVE-2026-87902 and the GitHub advisory GHSA-7hp8-65ch-5whp. Patchstack’s follow-up analysis reports the first exploitation attempt at its firewall at 11:49 UTC on 22 September and the first attempt to write a file through pearcmd at 15:34 UTC that day. It also says the payloads matched the encoding the patch addresses, which it reads as attackers working from the public diff. Scanning tools followed, including a named Nuclei template.

CISA added the CVE to its Known Exploited Vulnerabilities catalog on 25 September 2026 with a due date of 28 September, according to the catalog entry we checked on 15 November. The sources do not give the exact minute the patch became public, so we do not claim a number of hours between patch and first probe. What they support is simple: the first attempts came the same day.

That is the argument against “wait three days and see if anyone complains”. For a critical, unauthenticated bug the danger arrives with the patch. For the checks that tell you whether a site was in the worst case, see our WordPress 7.1.2 path traversal walkthrough on a sister site. A firewall buys hours at best, which we cover in your host’s firewall is not the patch.

7.1.3: seven fixes, none of them a headline

The 6 October post lists no CVE IDs. Its seven security fixes include a stored XSS on the Comments admin page, a second-order SQL injection in the WXR export, Author-role users making posts sticky and an unauthenticated disclosure of comments on private posts. It says to update immediately and that automatic background updates will start by themselves. Nobody triages seven fixes across 60 sites reliably on release morning, so “every security release goes out today” costs almost nothing and removes the judgement call.

7.1.4: when the update process is the weak point

The 28 October notes list 22 vulnerabilities, 17 of them as separate advisories according to Patchstack. One is “a race condition during core updates that could lead to remote code execution”, reported by Umut Bayram. Patchstack says it needs no account, but an attacker has to hit a window of seconds while an update runs, and wp-content/upgrade/ must be reachable over the web. It rates the attack complexity as high, does not call it practical to exploit, and reports no exploitation in the wild. The code path reaches back to WordPress 2.8, per the same article.

The detail that matters for a policy is Patchstack’s own advice: the window reappears on every update, including unattended ones, so automatic updating does not remove the exposure, and a PHP-level firewall cannot block it. The fix is to update to 7.1.4 (or your branch’s backport) and to block web access to wp-content/upgrade/ at the web server. Between updates that folder should hold only an index.php. Check yours:

# Checked on 15 Nov 2026. Expect only index.php between updates.
ls -la wp-content/upgrade/
curl -s -o /dev/null -w '%{http_code}\n' https://example.com/wp-content/upgrade/
# nginx: deny web access to the upgrade working folder (our example, test on staging)
location ^~ /wp-content/upgrade/ {
    deny all;
}

On Apache 2.4 the same idea is a .htaccess file inside that folder with Require all denied. If you are on shared hosting, ask the host. Patchstack’s analysis is the source for the risk and the mitigation; the two config snippets are ours, so test them before you roll them out.

What is the update policy by update type?

Adjust this for your own sites, but keep the shape: security is fast and automatic, features are slow and tested.

Update type

Timing

Where to test

Rollback

Core security release (7.1.2, 7.1.4)

Same day, automatically. Confirm within hours that it ran.

Production, with the five-point smoke test right after. Staging first only for sites with heavy custom theme code.

Restore the pre-update backup. Do not downgrade core on a security release unless you have no other choice.

Core minor maintenance release (7.1.3)

Same day or next working day, automatically.

Production smoke test. Keep one early-warning staging site per hosting stack.

Restore the backup. If one plugin broke, deactivate only that plugin.

Core major release (7.2 is planned for 8 December 2026)

Staged: a copy first, then a low-risk site, then the rest over one to two weeks.

Full staging copy with real data. Click the money paths: login, checkout, forms.

Restore the backup taken just before. Major releases can change the database, so a file-only downgrade is not enough.

Plugin security release

Same day. Read the changelog line first.

Production for most plugins. Staging first for payment, membership, login and form plugins, but the pass takes minutes.

Reinstall the previous version, unless that is the vulnerable one. Then deactivate until a fix lands.

Plugin feature release

Wait 3 to 7 days for large plugins, then staging, then batches.

Staging copy with the same theme and plugin set as production.

Restore the backup or reinstall the previous version.

Theme update

Security fix: same day. Feature or redesign: staging first. Check child theme overrides.

Staging: home page, a post, an archive, cart and checkout.

Switch back to the previous theme version. Keep the old theme folder until the new one is proven.

PHP or database version change

Treat as a project, not an update. Plan it on a calendar.

Full staging copy on the target PHP and database version.

Host-level snapshot or backup restore.

The 7.2 date comes from the official beta announcement as we verified it on 15 November. Our WordPress 7.2 upgrade calendar covers the PHP and database side of that release in detail.

The word “automatically” matters as much as “same day”. A policy that depends on one person logging in on release day fails the first time that person is on holiday.

What should a staging site and backups look like for this policy?

Staging is for the slow track, backups are for every track. The WordPress upgrade documentation is blunt about this: back up the database and all files, and verify that the backups are there and usable, calling that step essential. A backup you have never opened is a hope, not a backup.

  • One staging site per hosting stack. If your clients run on three different hosts, three staging sites updated first give you an early warning for each. Use the same PHP version, theme and plugins as production.
  • Staging with real data, for money paths only. Copy the database for shops, memberships and booking sites. For a five-page brochure site, a staging copy is overkill and a backup plus a smoke test is enough.
  • A backup before every update run. Files and database together, taken by the host, a plugin or a scheduled script. For a quick database copy, wp db export before-update.sql writes one to the current folder.
  • A restore you have tried. Once a quarter, restore one site to a scratch location and open it. Note how long it took.
  • A short list of sites that skip automation. Each entry needs a named owner and a reason, and the list gets reviewed monthly. If it grows, the policy is failing.

For a one-site owner, the simple version is: leave core automatic updates on, turn on plugin auto-updates for plugins you trust, keep daily backups, and check the site after the email arrives. For an agency, the table above is the policy and the loop below is the proof.

How do you check that a site actually updated?

Because the setting says what WordPress is allowed to do, not what it did. A site can show auto-updates on and still sit on an old version for weeks. The usual causes are a constant that overrides the setting, a plugin or mu-plugin that filters updates off, WP-Cron that never runs, or a file system the web server cannot write to. Three steps per site, in order:

# Checked on 15 Nov 2026 against the WP-CLI command pages
# 1. What version is running? (reads files, works even if the database is down)
wp --path=/var/www/example.com core version

# 2. What does the site allow? A missing constant prints an error: that means "default".
wp --path=/var/www/example.com config get WP_AUTO_UPDATE_CORE
wp --path=/var/www/example.com config get AUTOMATIC_UPDATER_DISABLED

# 3. Did the update run? --minor lists same-branch updates only (the security-release case).
wp --path=/var/www/example.com core check-update --force-check
wp --path=/var/www/example.com core check-update --minor --force-check

If step 3 lists an update and the release is more than a few hours old, the automatic update did not happen. Apply it with wp core update --minor, then find out why it did not run on its own. A value of false for WP_AUTO_UPDATE_CORE, or true for AUTOMATIC_UPDATER_DISABLED, explains it at once.

A loop for many sites

Keep one WordPress path per line in a text file. This loop prints the version and both constants for every site, so one glance shows which sites need attention. For remote servers, WP-CLI’s --ssh option works in place of --path.

#!/usr/bin/env bash
# sites.txt: one WordPress path per line  (checked on 15 Nov 2026)
while IFS= read -r path; do
  [ -z "$path" ] && continue
  ver=$(wp --path="$path" core version 2>/dev/null)
  auto=$(wp --path="$path" config get WP_AUTO_UPDATE_CORE 2>/dev/null || echo "not set")
  off=$(wp --path="$path" config get AUTOMATIC_UPDATER_DISABLED 2>/dev/null || echo "not set")
  printf '%s\t%s\tWP_AUTO_UPDATE_CORE=%s\tAUTOMATIC_UPDATER_DISABLED=%s\n' "$path" "$ver" "$auto" "$off"
done < sites.txt

Run it on release day and again 24 hours later. Any site still behind goes on a short list that is worked the same day.

What should you test after every update?

Five checks, in this order, each short enough to run across a fleet:

  1. The site responds. The home page and one post return a 200 status. curl -s -o /dev/null -w '%{http_code}\n' https://example.com/ prints only the code.
  2. Core files are intact. wp core verify-checksums compares core files with the checksums from WordPress.org. It checks core only, not plugins or themes. A mismatch right after an update can mean a failed copy.
  3. Login and admin work. Log in with a real account, open the dashboard and the Updates screen.
  4. The money path works. Submit one form, add a product to the cart or open checkout. On a live store, stop before the payment step.
  5. The error log is quiet. Read the last 50 lines of the PHP error log for fatal errors that were not there before.

How do you roll back a bad update?

In order of preference:

  1. Restore the pre-update backup. Files and database together. This is the only option that fully undoes a major core release.
  2. Deactivate the plugin or theme that broke. If the fatal error names a plugin, wp plugin deactivate plugin-slug usually brings the site back in seconds and keeps the security update in place.
  3. Reinstall the previous version. wp plugin install plugin-slug --version=1.2.3 --force, but only if the older version is not the vulnerable one.
  4. Downgrade core, as a last resort. wp core download --version=7.1.3 --force --skip-content replaces core files and leaves wp-content alone. On a security release you are putting the vulnerable code back, so do it behind a maintenance page and plan the real fix the same day.

On a security release, “go back to the old version” is the worst instinct, because the old version is the one with the hole. Disable the broken piece, keep patched core and fix forward.

What if your site runs an older WordPress branch?

WordPress backports security fixes to older branches as a courtesy. The 7.1.4 notes list a fixed release for each branch down to 4.7.39, say that 4.6 and earlier no longer receive security updates, and remind readers that only the most recent version of WordPress is actively supported. So an old site can take a small security update without a major jump, but it is still an old site.

Do not assume a backport landed. Check three things. First, wp core version must be at or above the patched release for your branch, and the release notes list that number. Second, wp core check-update --minor --force-check should show a same-branch update if one exists; if it says up to date while the version is below the patched number, something is blocking the check, such as a host that pins versions or a filter. Third, wp core verify-checksums confirms the files match the stated version. There is no separate “security patch applied” flag, and a firewall rule is not the same as fixed files.

Common mistakes people report

These are recurring problems from the WordPress documentation, the WordPress.org support forums and vendor guides, paraphrased, and checked on 15 November 2026.

  • A constant overrides the dashboard. Site owners turn on auto-updates in the admin and nothing happens, because WP_AUTO_UPDATE_CORE or AUTOMATIC_UPDATER_DISABLED in wp-config.php wins. The upgrade documentation says the constant overrides the Updates-screen setting.
  • A version control checkout silently turns core updates off. Sites deployed from a Git repository often never receive core updates, because WordPress detects the checkout. The same documentation page describes this exception. Update those sites through your deployment instead, and put them on the check loop.
  • Plugin updates rolled back by a cache plugin. One forum reporter on 6.6 and later saw auto-updates fail and roll back with WP Super Cache, with a cURL error during the post-update home page check. They fixed it by turning off page compression or rejecting a wp_scrape_key= URL string. That is one reporter’s fix, not an official diagnosis; read the thread (posted November 2024) before copying it.
  • The site is stuck in maintenance mode. An interrupted update can leave a .maintenance file in the site root. Hosting and vendor guides such as Jetpack’s and Themeisle’s agree on the fix: wait a few minutes, then delete the file, and if it returns, read the PHP error log.
  • Paid plugins that cannot update without a licence. Auto-updates for premium plugins stop when the licence has lapsed or the vendor feed is unreachable, and the site looks fine while falling behind. Jorijn’s update recovery guide lists a paid plugin without a valid licence among the signals to check. Put licence expiry on the same loop as versions.
  • Trusting a firewall during the update itself. After 7.1.4, Patchstack said a PHP-level firewall cannot block the update-window race condition. The server has to deny access to wp-content/upgrade/.

What should you tell clients?

Clients do not want a lecture. They want three answers: was my site at risk, is it fixed, and what do you need from me. A security-release note can be this short: “WordPress released a security update on [date]. Your site was updated on [date and time, UTC]. We confirmed the new version is running and checked your home page, login and [main action]. No action is needed from you.” For a feature release, say what you are testing, when the live update is scheduled and that nothing changes for visitors until then.

Three habits make these believable: state the date and time, say what you checked (not “all good”), and say plainly when a site was behind. This is engineering guidance, not legal or compliance advice. If a contract or regulation sets update deadlines, follow those.

Questions people ask

Are WordPress auto-updates safe to turn on for every site?

For core security and minor releases, yes, and it is the safer default, because the fixes are narrow and the cost of delay is higher than the cost of the update. For plugins, auto-updates suit simple sites. Keep payment, membership and heavily customised sites on the staged track, and always have a backup that runs before the update.

Does WordPress update plugins automatically?

Not unless you turn it on. Core minor releases update by default on most sites; plugins and themes need auto-updates enabled per item in the admin, with wp plugin auto-updates enable, or with the auto_update_plugin filter.

How do you know if a site was exploited before it updated?

The version number will not tell you. Look at access logs around the release window, then review recently modified PHP files, unknown administrator accounts and unexpected scheduled tasks. For 7.1.2, Patchstack suggests looking for feed or OPML output returned from a normal page URL, which signals a first-stage probe that worked. If the site was exposed and you find anything, treat it as an incident, not a patch.

Where to go from here

A written policy, a loop that proves it worked and a rollback you have already rehearsed turn release day from a scramble into a routine. If you would rather not run that routine for every client yourself, our team does it as part of WordPress maintenance, with staging-tested updates and written reports. Our WordPress security services cover the audit side when a site was behind or something looks wrong. Sources were checked on 15 November 2026, and we will update this page when the next release changes anything above.

Part of the Wbcom Designs family

The all-in-one WordPress community stack

Also ours: wbcomdesigns.comvapvarun.combrndle.com