Your Backup Plugin Is Still a Plugin: How to Check Backup and Migration Tools Across Your WordPress Sites

Most people think of the backup plugin as the safety net. It’s the thing you reach for when everything else has gone wrong. So it’s easy to forget that it’s also just another plugin, with its own updates and its own security holes.

Two reports from Wordfence in October 2026 made that point nicely, and in a way that’s worth understanding even if you don’t run either plugin.

What happened

Duplicator (more than a million active installs). Wordfence found that someone with no account could plant a specially crafted value in an ordinary WordPress comment. On its own, it does nothing. But if an administrator later built a Duplicator package that included that comment, and then used the package to migrate the site, the installer would treat the stored value as code and run it. Duplicator Free and Duplicator Pro were both affected. The fix is in Duplicator 5.0.0 and later. This one has a public CVE (a listed, known security hole): CVE-2026-82814.

Backuply (600,000+ active installs). Here, a logged-in user with only subscriber access could hide a payload in their profile’s Biographical Info field. When an administrator later restored a database backup containing it, the payload ran during the restore and could change site settings so a newly registered account became an administrator. The fix is in Backuply 1.5.9 and later (CVE-2026-93953).

Wordfence hasn’t reported either one being used against real sites. Both are patched. But the shape of them is the lesson.

Why this kind of bug is sneaky

Both attacks wait. The bad data sits quietly in normal-looking content until someone runs a migration or a restore.

Think about when you actually restore or migrate a site. It’s rarely on a calm Tuesday afternoon. It’s when a site is broken, a client is ringing, or you’re moving hosts against a deadline. That’s exactly the moment you’re least likely to stop and check which version of the backup plugin made that archive.

So my rule is simple: backup and migration plugins get updated with the same urgency as anything else, and I don’t treat an old backup as automatically trustworthy.

How to check your sites

1. Find out which sites run backup or migration plugins

On one site, that’s a quick look at the plugins screen. Across twenty or fifty sites, it’s the part people skip. You need a list: which sites have Duplicator, Backuply, UpdraftPlus, All-in-One WP Migration or anything similar, and which version each one is on.

2. Update to a fixed version

For these two:

  • Duplicator: 5.0.0 or later (Free and Pro).
  • Backuply: 1.5.9 or later.

Check the changelog of whatever backup tool you do run. Security fixes don’t always get a loud announcement.

3. Make a fresh package or backup after updating

Wordfence’s advice for Duplicator is specific: updating the plugin doesn’t rebuild packages that already exist, because each package carries the installer from the version that created it. Before you use a package made with an affected version for a normal migration or import, create a fresh one with the updated plugin where you can.

For any backup tool, it’s a sensible habit to take a new backup after a security update, so your most recent restore point was made by fixed code.

4. Keep a copy off the server

A backup sitting on the same server as the site is only half a backup. If the server has a problem, so does your copy. Store at least one copy somewhere else.

5. Write down what changed

When you update a backup plugin, or anything else, note when it happened. If something misbehaves later, “what changed and when” is the first question you’ll want answered.

Where CMS Inspect fits

That checklist is easy for one site and tedious for a fleet. It’s the everyday job CMS Inspect was built for:

  • One dashboard for versions and pending updates across every WordPress and Joomla site, so you can see which sites run a given plugin and which ones are behind.
  • Updater and installer to queue updates, run them now, retry, and watch their state, with command logs.
  • Bulk operations to apply updates across many sites instead of logging in to each one.
  • Backups that generate database and file backups and upload them to Google Drive or Dropbox, so you have an off-server copy.
  • External update detection, so updates done outside CMS Inspect (by a client, another developer, or the host) still show up in the timeline.
  • Audit history and reports so you can show clients what was patched and when.

Core is free, and advanced operations are $1 per active site a month. You can see the pricing or start free.

The short version

The backup plugin isn’t special. Update it like everything else, make a fresh backup once you have, keep a copy off the server, and know which of your sites are running what. The worst time to find out your safety net had a hole is while you’re falling.

Sources: Wordfence, Duplicator PHP object injection and Backuply SQL injection.