Security updates in hours, not half a day: your sites now check in with ToggleWP Cloud every hour
WordPress checks for plugin updates twice a day. Most of the time that’s fine. But when a plugin author ships a security fix, the fix is public from the moment it’s released. Anyone can compare the old version with the new one to see what was wrong, and every hour a site spends on the old version is an hour it can be attacked.
With the latest ToggleWP plugin, your sites check in with ToggleWP Cloud every hour. That gets security updates onto your sites sooner, and it makes sure vulnerability alerts and Update Guard results reach every site, even on hosts that block incoming connections.
The problem: half a day is a long time
Say you look after 40 client sites, and 25 of them run the same forms plugin. Its author releases a version that fixes a security hole before a CVE has been published.
One of your sites happens to check for updates ten minutes later and sees the new version. The other 24 won’t look again for up to 12 hours. If they have automatic updates on, they’ll install it eventually. But “eventually” is the gap attackers count on, with the time from publishing an update to working exploit decreasing from days to hours.
ToggleWP Cloud already knows about the update the moment that first site reports it. Now it can do something about it.
Early updates: one site finds it, the rest follow within the hour
Every hour, each site asks ToggleWP Cloud: “Is there anything I should know about?” If another of your sites has reported a newer release of a plugin this site runs, Cloud says so, and the site checks for updates straight away instead of waiting for WordPress’s own schedule.
What happens next is up to each site’s own settings, exactly as before:
- Plugins with automatic updates on install the new version within minutes.
- Plugins without automatic updates show the update in wp-admin straight away, so it’s there the next time you or your client logs in.
- Premium plugins protected by Update Guard are still checked before they install. A site checking earlier just means the check starts earlier.
You choose which updates this applies to, under Vulnerabilities → Settings → Early updates:
- Security fixes only (the default): only when the newer version fixes a security issue. That means either the plugin has a known vulnerability in the Wordfence Intelligence feed, or ToggleWP Cloud has read the new release’s notes and found a security fix.
- All plugin updates: whenever any of your sites has seen a newer version.
- Off: sites follow WordPress’s normal 12-hour schedule.
Each site is told about each new version once. If a site can’t get an update, for example because a premium licence has expired, it won’t keep checking every hour.
Security update emails that tell you what happened
When a plugin update’s release notes say it fixes a security issue, ToggleWP Cloud emails you. That email used to list your other sites with the same plugin as “hasn’t picked up this update yet”, which left you to work out what to do about each one.
Now the email says what has happened on every site running the plugin:
- Updated: the site is already on the fixed version.
- Updating automatically: the site has the update and installs it by itself.
- Update waiting in wp-admin: the site has the update, but automatic updates are off for that plugin, so someone needs to click Update.
- Told to check for updates: ToggleWP Cloud has told the site about the release, and it hasn’t reported back yet.
- Will be told at its next hourly check-in: the site will hear about it within the hour.
- Not checking in hourly: the site needs ToggleWP 2.0.5 or later, and WP-Cron running, to be told early.
So instead of a list of sites to chase, you get a short list of the ones that actually need you.
Or wait an hour, and hear what your sites did
Under Vulnerabilities → Settings → Security updates you can choose when the email is sent:
- Straight away (the default): you hear about the update as soon as ToggleWP Cloud finds it, along with where each site has got to. You can trigger an update via your existing site management tool like WP Umbrella.
- After the sites have had an hour to update: ToggleWP Cloud holds the email while your sites are told and install the update, then sends it with the result. Most sites will show as Updated, and the ones that need you stand out.
The held email goes out as soon as there’s nothing left to wait for, and never more than about an hour after the update was found. Emails to each site’s own admin are never held.
Alerts that reach every site, whatever the host
Until now, when ToggleWP Cloud had news for a site (a new vulnerability match, or an Update Guard verdict on a premium update), it called the site to tell it.
That works on most hosting. But some hosts’ bot protection and firewalls block incoming calls they don’t recognise, and ToggleWP Cloud’s calls were sometimes among them. On those sites the news only arrived at the site’s next full report, up to 6 hours later.
Now the news waits for the site’s hourly check-in instead. Because the site makes the call, out to ToggleWP Cloud, it gets through on any host that lets the site reach the internet. That covers the hosts that blocked us before.
In practice:
- New vulnerabilities from the Wordfence feed reach each affected site, and its admin alert emails, within the hour.
- Update Guard verdicts, including when you approve a held update, reach the site within the hour, and its automatic update goes ahead.
Run your own servers? Turn on instant pings
If you host your clients’ sites yourself, you can have the news delivered in seconds rather than within the hour.
Allow incoming calls from ToggleWP Cloud’s IP address on your servers, then turn on Vulnerabilities → Settings → Instant pings. ToggleWP Cloud then calls each site as soon as something changes, as well as leaving the news for its hourly check-in. That includes early updates: when one site reports a security release, your other sites are told to check for it in seconds, before the security update email is sent, so the email can already list them as told.
It’s safe to turn on even if only some of your sites will let the call through:
- Where the call gets through, the site acts on it straight away.
- Where a host blocks it, nothing is lost: that site picks the news up on its next hourly check-in.
If you move hosting later, or start allowing the IP address on more servers, there’s nothing else to change. Leave the setting on and every site that can be reached will be.
What you need
- The latest ToggleWP plugin (2.0.5 or later) on your client sites. Sites on older versions keep working as before.
- Vulnerability Monitor in the sites’ Feature Set, as for vulnerability alerts today.
- WP-Cron running, as it already needs to for automatic updates. If a site’s WP-Cron has stopped, ToggleWP Cloud already alerts you when that site stops checking in.
The hourly check-in is one small request per site, made by the site. No changes to your hosting or firewalls are needed.
In short
- Security updates spread across your sites within the hour of the first site seeing them, not up to 12 hours later.
- Vulnerability alerts and Update Guard results reach every site, even on hosts that block incoming connections.
- Security update emails say which sites have updated and which need you, and can wait an hour to report the result.
- If you run your own servers, instant pings deliver them in seconds, with the hourly check-in as a backup.
