Skip to content
WP Hack FixEst. 2005

Security news

Backuply: restoring a backup could hand a subscriber your site

Published · Disclosed October 15, 2026 · By Adam Taylor

PluginVulnerableFixed in
Backuply – Backup, Restore, Migrate and Clone<= 1.5.81.5.9

Backups are supposed to be the safe way out of trouble, which is what makes this one awkward. Wordfence has disclosed a flaw in Backuply, a backup plugin on more than 600,000 WordPress sites, where restoring a backup is the step that hands an attacker your site.

It’s rated 8.0 out of 10 and was fixed in version 1.5.9, released October 1.

Am I affected?

You’re affected if your site runs Backuply 1.5.8 or earlier. Check the version under Plugins in your dashboard.

The attacker needs an account on your site, but only the lowest kind: a subscriber. So the risk is real if anyone can register on your site: membership sites, shops where customers create accounts, course sites, or any site with “Anyone can register” ticked under Settings → General.

What an attacker could do

Every WordPress user has a Biographical Info box on their profile. An attacker with a subscriber account fills theirs with a carefully written instruction for your database instead of a bio. On its own, that does nothing.

The trap springs later. Backuply copies that bio into your backups, and when an administrator restores one of those backups, Backuply’s restore process runs the hidden instruction against your database. The instruction quietly changes two site settings: it opens registration to everyone, and it makes every new account an administrator. The attacker then signs up again and walks in as an admin.

Nothing happens until someone restores. But people usually restore a backup when something has already gone wrong, which is exactly when nobody is checking the settings afterwards.

What to do

  1. Update Backuply to 1.5.9 or later. Plugins → Update. The fix is in the restore process, so update before you restore anything, including older backups.
  2. Check two settings under Settings → General: “Membership” (is “Anyone can register” ticked when you didn’t intend it?) and “New User Default Role” (it should almost never be Administrator). If either changed without you changing it, treat that as a warning sign.
  3. If you’ve restored a backup recently, check your users list for administrator accounts you don’t recognise, sorted by newest first.
  4. If you find an admin you didn’t create, removing it isn’t the end of the job. Admin access is enough to plant files that bring the attacker back. Get the site checked properly.

There’s no sign of anyone using this in attacks yet. Because it only fires on a restore, it’s a slow trap rather than a quick one, and that also means a booby-trapped bio could already be sitting in your backups, waiting.

On a Protect plan? Plugin updates are part of what we do, so this one is covered.

Worried your site's already been hit?

If something looks wrong, we'll check it and clean it up. If we can't fix it, you don't pay.

We reply within 1 business day (Mon–Fri, 9–5 ET)