Skip to content
WP Hack FixEst. 2005

Security news

Duplicator: a booby-trapped comment can go off when you migrate your site

Published · Disclosed October 20, 2026 · By Adam Taylor

PluginVulnerableFixed in
Duplicator<= 1.5.175.0.0
Duplicator Pro<= 4.6.105.0.0

If you use Duplicator to move or copy WordPress sites, this one is worth knowing about before your next migration. Wordfence has disclosed a flaw in Duplicator, a migration and backup plugin on more than 1 million sites, rated 8.8 out of 10.

It was fixed in version 5.0.0, released September 8, for both the free plugin and Duplicator Pro.

Am I affected?

You’re affected if your site runs Duplicator 1.5.17 or earlier, or Duplicator Pro 4.6.10 or earlier. Check the version under Plugins in your dashboard.

The attacker doesn’t need an account. They only need to be able to leave a comment, and turning on comment moderation doesn’t stop it, because comments waiting for approval are still stored and still get packaged.

How the attack works

Like the Backuply flaw earlier this month, it’s a trap that waits for you.

  1. The attacker leaves a comment on your site. It looks like gibberish, but it’s a carefully built instruction.
  2. Later, you create a Duplicator package to move or copy the site, and the comment goes into it along with everything else.
  3. When that package is used to migrate, Duplicator processes the comment in a way it shouldn’t, and the instruction runs.

On the free version, that lets the attacker run commands on the server. On Pro, it lets them delete a file of their choosing, and deleting the right one can lead to a full takeover.

Making a backup on its own doesn’t trigger it. The danger is in using a package for a migration or import.

What to do

  1. Update Duplicator or Duplicator Pro to 5.0.0 or later. Plugins → Update.
  2. Build a fresh package before your next migration. Packages made with older versions still contain the old, vulnerable installer. It’s fine to keep them as a fallback, but don’t use them to move a site.
  3. Clear out junk comments sitting in your pending or spam queues before you make a package. If a comment is just a long string of random-looking characters, it isn’t a real comment.
  4. Delete leftover installer files from past migrations. If an old installer.php or similar is still sitting on a live server, it doesn’t need to be there.
  5. If comments are turned off on your site, the route Wordfence demonstrated is closed, but update anyway.

There’s no sign of anyone using this in attacks yet. Because it only fires during a migration, it’s a slow trap rather than a quick one, and a booby-trapped comment could already be sitting on your site, 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)