Research · 10 min read

WordPress Backup Plugin Vulnerability: 4 Bugs That Wait

By WP Vanguard Team

Four backup and migration plugins disclosed the same kind of flaw in two months. In each one, an attacker plants something harmless-looking on your site, like a comment, a trackback or a profile bio, and nothing happens until you run a backup, a restore or a migration. Then the plugin reads that stored text and executes it. This WordPress backup plugin vulnerability pattern hit All-in-One WP Migration, Backuply, Duplicator and Prime Mover, which together have about 6.6 million active installs.

Every one of them is patched. The point isn't that these four are uniquely sloppy. It's that a migration plugin's job is to read your whole database and rewrite it, and your database is full of text that strangers typed in. If you only take one thing from this post: update these plugins before your next migration, and don't migrate a site you haven't checked.

WordPress Backup Plugin Vulnerability: 4 Bugs That Wait
On this page

4

backup and migration plugins with a payload that waits for the admin, Aug 25 to Oct 24

All-in-One WP Migration, Backuply, Duplicator, Prime Mover. 6.6M installs combined.

Four plugins, one attack shape

Here's what each disclosure looks like side by side. Install counts are current wordpress.org figures.

Plugin Installs Planted through Fires when Result Fixed in
All-in-One WP Migration 5,000,000 A trackback, no login An admin restores a backup SQL injection, then code execution 7.110
Duplicator 1,000,000 Public site content, no login An admin builds a package and migrates PHP object injection, then OS commands 5.0.0
Backuply 600,000 A Subscriber's profile bio An admin restores a backup SQL injection that makes new accounts admins 1.5.9
Prime Mover 10,000 A base64 string in a comment, no login An admin exports or restores PHP object injection 2.2.2

Three of the four need no account at all. The fourth, Backuply, needs a Subscriber login, which any site with open registration hands out for free. We covered why that matters in our report on subscriber-level vulnerabilities and open registration.

What none of them need is for the attacker to be around when it fires. The planting request is ordinary comment or profile traffic. A firewall that inspects requests as they arrive sees nothing worth blocking, because at that moment the payload does nothing.

Why a WordPress backup plugin vulnerability waits for you

Moving a WordPress site means changing its URL everywhere it's stored. That sounds like a simple find-and-replace, but a lot of WordPress data is serialized PHP, where every string carries its own length. Replace old.example with new-site.example inside a serialized value without fixing the length, and the value breaks.

So migration plugins do the careful thing. They walk every row, unserialize each value, replace the strings inside it, and serialize it again. That's correct for your own settings. It's dangerous for a comment, because a comment is text a stranger chose. If the stranger typed a serialized PHP object, the plugin now builds that object, and PHP runs its magic methods as it does.

Restores have the same problem from another angle. A backup is a big SQL file the plugin wrote from your database and later plays back. If it wrote stored text into that file without escaping it properly, a quote in a profile bio becomes the end of one SQL statement and the start of another. That's what Backuply and All-in-One WP Migration got wrong.

Key finding

A migration plugin treats your database as trusted, and your database holds text from every commenter, pinger and registered user you've ever had. Planting a payload costs one comment. The admin's next migration does the rest.

The four cases

All-in-One WP Migration (August 25)

CVE-2026-19949 starts with a trackback, which WordPress accepts from anyone on the internet. The crafted trackback carries backslash and quote sequences that do nothing until a restore rewrites URLs through SQL queries that don't handle them. The researcher showed it leaking the plugin's secret key, which leads to code execution. Our full All-in-One WP Migration breakdown covers the chain step by step. Thirteen days after the fix, about 65 percent of installs were still on a vulnerable build.

Backuply (October 16)

CVE-2026-93953 lives in the backup file itself. Backuply wrote a user's Biographical Info into the SQL dump without escaping it, so a Subscriber could put SQL in their bio and wait. When an admin restored that backup, the injected SQL ran with full database rights. The published path flips the default role to administrator and turns on registration, so the attacker's next signup is an admin.

Duplicator (October 21)

CVE-2026-82814 is PHP object injection. An attacker stores a serialized object in public content, and Duplicator deserializes it during a migration or import. The free plugin ships a gadget chain that reaches OS command execution, and Pro's can delete a file such as wp-config.php. One detail matters for timing: the package has to be built after the payload is stored. A package you built before the comment arrived is clean.

Prime Mover (October 24)

CVE-2026-115806 is the plainest of the four. Anyone can post a comment holding a base64-encoded serialized object. When an admin runs a Prime Mover export or restore, its search-and-replace decodes and unserializes it with no class limits. The gadget chain comes from the Freemius library the plugin bundles, so the site doesn't need any other plugin installed. Wordfence rates it 9.8, the highest of the four.

The patches came before the disclosures

All four vendors shipped the fix before the CVE went public, which is how coordinated disclosure is meant to work.

Fix shipped, then CVE published
  1. Aug 20AIOWM 7.110CVE public Aug 25, 5 days later
  2. Sep 8Duplicator 5.0.0CVE public Oct 21, 43 days later
  3. Oct 1Backuply 1.5.9CVE public Oct 16, 15 days later
  4. Oct 19Prime Mover 2.2.2CVE public Oct 24, 5 days later

We checked each release date against the wordpress.org plugin repository. Duplicator's lead is the longest: its 5.0.0 release, which rewrote the plugin, went out 43 days before the CVE. A site with auto-updates on was covered long before anyone could read about the bug.

The catch is the sites that don't update. As the All-in-One WP Migration numbers showed, a patch two weeks old still leaves most installs exposed, and migration plugins are exactly the kind of tool people install once and forget. Our database also shows Prime Mover with no fixed version as of today. The 2.2.2 changelog credits Wordfence for "hardened unserialize implementation to prevent object injection", and the code diff confirms it, so the feed just hasn't caught up.

What changed in the code

Prime Mover's fix is a clean example of the right repair. Before 2.2.2, its search-and-replace called PHP's unserialize() directly:

PHP
if (is_string($data) && ($unserialized = @unserialize($data)) !== false) {

2.2.2 routes every call through one helper that only allows plain stdClass objects:

PHP
return @unserialize($serialized_string, [
    'allowed_classes' => [
        'stdClass',
    ]
]);

With allowed_classes set, a planted object of any other class comes back as an inert __PHP_Incomplete_Class, so no magic method runs and the gadget chain never starts. It's the same fix we found in three other plugins in our unserialize vulnerability analysis. Duplicator's fix arrived inside the 5.0.0 rewrite, so there isn't a single line to point at.

The two SQL cases need a different repair: escape stored values when they're written into the dump, and use prepared statements when they're read back. Either way, the lesson is the same. Data that came out of your own database isn't trusted just because it was already there.

Before your next migration: a checklist

None of this means you should stop using backup plugins. A backup is still the thing that saves you after a hack. It does mean a migration deserves the same care as an update.

  1. Update first. You need All-in-One WP Migration 7.110 or later, Backuply 1.5.9, Duplicator 5.0.0 and Prime Mover 2.2.2. Duplicator Pro's fix is also 5.0.0. wp plugin list --fields=name,version shows what's installed.

  2. Look for planted objects before you migrate. Serialized PHP objects start with O: followed by a number, and base64 of O: starts with Tzo. Neither belongs in a comment. This query lists comments containing either pattern:

    Terminal
    wp db query "SELECT comment_ID, comment_type, LEFT(comment_content, 80) FROM $(wp db prefix)comments WHERE comment_content REGEXP 'O:[0-9]+:\"' OR comment_content LIKE '%Tzo%'"
    

    It's a quick filter, not proof. A hit is worth reading.

  3. Check recent Subscriber profiles too. The comment query doesn't cover the profile bio route Backuply used, so skim the bios of accounts created since the plugin went public.

  4. Don't restore backups you didn't make, or that predate a cleanup. A backup taken while a payload sat in the database carries the payload with it.

  5. Deactivate migration plugins between uses. Most of these code paths only run while the plugin is active. If you migrate twice a year, it doesn't need to be active the other 363 days.

  6. Remove Everest Backup. CVE-2026-39802 is an unauthenticated remote code execution (CVSS 9.8) in 2.3.13 and earlier, with no fixed version, and the plugin hasn't been updated since August 20. SiteVault had a 9.8 of its own this month, fixed in 1.5.20.

If a site ran a vulnerable version and you've already migrated or restored since the plugin went public, treat it as possibly compromised. Check for admin accounts you didn't create and work through the signs your WordPress site has been hacked before you trust it again. If something turns up, our WordPress malware removal guide covers the cleanup.

What plugin developers should take from this

If your plugin reads stored content in bulk, which covers backup, migration, search-and-replace, export and caching tools, you're in the same spot. Three rules cover it:

  • Never call unserialize() or maybe_unserialize() on stored content without allowed_classes. If you need objects, list the exact classes.
  • Escape every value as you write it into a SQL dump, and use $wpdb->prepare() for anything you read back.
  • Treat a bundled library as part of your attack surface. Prime Mover's gadget chain came from Freemius, which it didn't write.

This class shows up across far more than backup tools. We traced it through dozens of plugins in our research on PHP object injection in WordPress plugins.

Check your sites

Run a free scan to check your installed plugin versions against our vulnerability database, including every plugin named here. The weekly patch list has this week's other fixes, and /vulnerabilities has every disclosure we track.

References

Related reading

Get weekly WordPress security tips

Vulnerability alerts, plugin updates, and security guides. No spam. Unsubscribe any time.