Duplicator ≤ 1.5.17 / Pro ≤ 4.6.10: A Visitor Can Booby-Trap Your Next Migration (CVE-2026-82814, CVSS 8.8)

Running Duplicator on your site? Check it against CVE-2026-82814 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your Duplicator is in the affected range (≤ 1.5.17), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

Duplicator ≤ 1.5.17 / Pro ≤ 4.6.10: A Visitor Can Booby-Trap Your Next Migration (CVE-2026-82814, CVSS 8.8)

Some vulnerabilities attack your site right away. This one waits. CVE-2026-82814 lets an unauthenticated visitor plant a booby-trapped payload inside a Duplicator site — and nothing happens until an administrator runs a routine backup migration or import, at which point the payload wakes up and executes. The trigger is an action your own admin takes, on a schedule attackers can afford to wait for.

What Happened

CVE-2026-82814 is an unauthenticated PHP object injection vulnerability in Duplicator and Duplicator Pro, the WordPress backup and migration plugins installed on more than one million sites. Wordfence published its analysis on October 20, 2026.

If this pattern sounds familiar, it should: it is the same "planted now, fired by a later admin backup action" shape as the Prime Mover flaw (CVE-2026-115806) disclosed the same week. Backup and migration plugins are becoming a category to watch, because their whole job is ingesting and reviving serialized site data.

Am I Affected?

Check the version your site announces. Duplicator's public readme discloses it, which means two things: attackers can enumerate vulnerable sites cheaply — and so can a defensive scanner. Our free mini-scan now reads exactly that version disclosure and flags sites in the affected range; it never tests the injection itself.

In wp-admin: Plugins → Installed Plugins → Duplicator. Anything at or below 1.5.17 (free) or 4.6.10 (Pro) is in the affected range.

What To Do Now

  1. Update to 5.0.0 or later — free and Pro alike.
  2. Until you have updated, do not run a migration or import. The planted payload only fires when an admin runs one; pausing that routine removes the trigger.
  3. Treat packages created while the vulnerable version was installed as untrusted. A package produced by a booby-trapped site can carry the problem to its destination.
  4. After updating, review recent admin activity and any newly created accounts or files — as with any object-injection exposure, the version number alone cannot tell you whether someone already planted a payload.

The Bigger Lesson

The most dangerous moment for a backup plugin is not when the attacker visits — it is when you do the routine thing the plugin exists for. Versions are public, triggers are patient, and "we only run migrations occasionally" is not a defense; it is the attack plan. Keep migration tooling patched like it is internet-facing code, because its inputs are.

Not sure which version your site is announcing to the world? Run the free check at preshipit.com/free-scan — Duplicator is one of the plugin versions it now reads.

Check Duplicator on your own site — free.

Our free WordPress Plugin Vulnerability Checker pulls Duplicator's current version from wordpress.org and lists the vulnerabilities our scanner checks for — CVE-2026-82814 included. No scan, no account.

Open the free plugin checker →

The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.

New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.

Running Duplicator on your site? Check it against CVE-2026-82814 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your Duplicator is in the affected range (≤ 1.5.17), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report