Updates and known vulnerabilities
The panel rates every plugin, theme and WordPress version on your sites against the advisories that wpvulnerability.net publishes, a free feed. The ratings appear wherever updates do: on each site’s WordPress tab and on Sites → Bulk management.

What is sent to wpvulnerability.net
Section titled “What is sent to wpvulnerability.net”The panel asks the feed about each plugin and theme by its slug, and about WordPress by its version number. It asks from the panel’s own server, at most once a day per slug, and keeps the answer. Whether an installed version is affected is worked out on the panel, so one answer serves every site. No site name, domain or visitor address is part of a request.
Each plugin’s slug also goes to wordpress.org’s directory, at the same time, to learn whether the plugin is closed. So does a theme’s, when the feed calls it closed. A closed one is asked about again after an hour.
Switch the ratings off
Section titled “Switch the ratings off”In Settings → Security, under WordPress updates & security, switch off Rate installed plugins and themes against known vulnerabilities. Then choose Save settings. The panel stops asking, and the ratings disappear. Updates keep working.
Read a rating
Section titled “Read a rating”A rating is the worst advisory that covers the installed version: critical, high, medium or low, with its CVSS score beside it. unrated means the advisory gives no severity. Each advisory names the release that fixes it, or says no fix available.
| Shown | Means |
|---|---|
| closed | wordpress.org closed the plugin or theme. It gets no updates from there, so replace it. |
| no data | The feed has no record of this slug, as with most premium plugins. That is not the same as safe. |
| not checked | The slug has not been looked up yet. The next scan does it. |
| check overdue | The saved answer is more than a day old. |
| check failed | The last lookup failed, and the previous answer is shown. |
| range unclear | The advisory names no version range the panel can evaluate. It may not apply. |
For a plugin, closed is wordpress.org’s word: the notice on a closed plugin’s page. The themes directory does not say which themes it closed, so a theme is shown as closed when the feed says so and the directory does not list it. If the directory does not answer, the panel keeps what it showed before.
Update one site
Section titled “Update one site”On the site’s WordPress tab:
- Update all updates everything that has an update, WordPress included.
- Update core updates WordPress only.
- Fix vulnerable, in the Security card, updates only what an available release fixes.
- Update on a plugin’s or theme’s row updates that one.
The first three ask first. Set the two switches, then choose Run it:
- Back up first takes a backup before anything changes, kept until you delete it or its keep period ends. The site’s Back up before updates decides it, as the next section explains. On a site set to Ask each time, the switch decides, and it starts on for a live site.
- Check the site answers afterwards fails the job if the site stops answering.
A row’s Update runs at once, with Check the site answers afterwards as last set on the page. On a site set to Ask each time, it opens the same dialog first.
Choose whether updates back up first
Section titled “Choose whether updates back up first”Since 0.3.0-beta.3 Back up before updates decides whether an update backs the site up first:
| Setting | Before an update |
|---|---|
| Always | The panel backs the site up. The dialog shows Back up first on, and locked. |
| Ask each time | Every update opens a dialog with Back up first. This is the default. |
| Never | No backup. The dialog shows Back up first off, and locked. |
Set it for every site in Settings, then Backups. A site’s own goes in Back up before updates on its Backups tab, whose first choice follows Settings. The site’s Updates card names the setting in force.
It holds for every update the panel starts: on the WordPress tab, in Bulk management, and over the API and MCP. An update schedule goes by its own Back up first switch instead.
Over the API, an update of a site set to Ask each time needs backupFirst, true or false.
Without it the request is refused, and an app connected over MCP is told to ask you first. For a
site set to Always or Never, backupFirst changes nothing.
What the update job does
Section titled “What the update job does”One job per site works in this order: the backup, the plugin updates, the theme updates, WordPress last, then the check. It fails when an update fails or the site stops answering, and its message names the backup to go back to. Nothing is rolled back by itself: restore that backup from the site’s Backups tab.
On a site hosted elsewhere, the check also asks WPL7 Connect. If the site answered before the update and stops answering after it, the plugins and themes the job updated are put back as they were. The job then fails, and its log says what was put back. WordPress itself is not put back.
With New vulnerabilities on in Settings → Monitoring, a vulnerability newly found on one of your sites is emailed to the alert address. The first email lists every one found so far.
Update many sites
Section titled “Update many sites”On Sites → Bulk management, select rows and choose Update. Each site gets its own job, with the same two switches, as Bulk management explains.
Update on a schedule
Section titled “Update on a schedule”- Open Automations → Schedules and choose New schedule.
- Under What, pick Update plugins, themes and WordPress. Under On, pick the sites.
- Under Options, tick Plugins, Themes or WordPress core. Tick Only updates that fix a known vulnerability to apply only those.
- Set Back up first and Check the site answers afterwards, and under When, how often it runs.
Each run reads the site again and decides then what to update. Its Back up first switch decides the backup for every site it updates, whatever their Back up before updates says. Its backups count as scheduled backups, so retention removes the old ones.
Limits
Section titled “Limits”- A new advisory shows once the panel next refreshes that slug, up to a day later.
- A theme wordpress.org closed shows as closed only if the feed flags it.
- A temporary closure, pending wordpress.org’s review, shows like a permanent one.
- On a hosted site, a failed update is not undone automatically. Restoring the backup also undoes every other change made to the site since.
- Where no fixed release exists, Fix vulnerable leaves the plugin as it is. Deactivating it is your decision.
- An update from the WP-CLI console, a recipe, WP Godmode or WordPress’s own automatic updates takes no backup first, whatever Back up before updates says.