Prime Mover ≤ 2.2.1: A Comment Can Booby-Trap Your Next WordPress Migration (CVE-2026-115806, CVSS 9.8)

Running Prime Mover on your site? Check it against CVE-2026-115806 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your Prime Mover is in the affected range (≤ 2.2.1), 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 →

Prime Mover ≤ 2.2.1: A Comment Can Booby-Trap Your Next WordPress Migration (CVE-2026-115806, CVSS 9.8)

Your backup plugin is probably the last thing you think of as attack surface. It should be near the top of the list. A critical vulnerability in Prime Mover – Backup and Migration, one of the most popular WordPress migration plugins (10,000+ active installs), means a comment left by a total stranger can sit quietly in your database — and turn into remote code execution the next time an admin runs a routine export or restore. Here's what happened, whether you're affected, and what to do about it.

What Happened

The flaw is tracked as CVE-2026-115806, a PHP object-injection vulnerability (CWE-502, deserialization of untrusted data) in Prime Mover, published by Codexonics. Wordfence — the researcher-finding firm that is also the CVE's assigning authority — scores it CVSS 9.8 and credits researcher Civitasmass with the discovery.

How It Works, Plainly

Prime Mover's migration feature includes a search-and-replace routine that runs over your site content during an export or restore. That routine takes serialized PHP data and unserializes it without restricting which classes may be created. That's the bug. The attack goes like this:

  1. An unauthenticated visitor posts an ordinary comment on your site. Hidden in the comment text is a base64-encoded serialized object — inert text, just sitting in the wp_comments table.
  2. Nothing happens. The comment can sit there for weeks.
  3. Later, an admin runs a Prime Mover export or restore. The search-and-replace routine processes the stored comment, decodes it, and unserializes the attacker's object.
  4. A gadget chain (a "POP chain") shipped inside the plugin's own bundled Freemius library turns that unserialize into remote code execution — no other plugin or theme required.

One honesty note, because the details matter: the published CVSS vector lists "no user interaction," but the technical chain does require that later admin export or restore to fire. This is not an instant, one-click takeover the moment a comment lands. It is a planted payload, triggered by a routine action admins perform all the time — which is exactly what makes it dangerous. The person who detonates it is you, on migration day, probably in a hurry.

Am I Affected?

Check your Prime Mover version: in wp-admin, go to Plugins → Installed Plugins and look at the version next to Prime Mover. 2.2.1 or anything older is in the affected range.

You can also check from the outside: like most WordPress plugins, Prime Mover announces its version in a public readme file. Our free mini-scan reads exactly this disclosure and flags Prime Mover versions in the CVE-2026-115806 range — paste your URL and it takes about a minute.

Two caveats, stated plainly. First, a version check tells you whether your version is in the affected range — it cannot tell you whether a booby-trapped comment is already stored in your database; only the comment review below covers that. Second, if the readme isn't readable from outside, that's "unconfirmed," not "safe" — check in wp-admin instead.

The Patch Confusion, Handled Straight

Here's where this one gets messy, and we'd rather show you both sources than pick one:

Those can both be true at once — a vendor can ship a hardening release before the assigning authority has verified and recorded it as the fix. Our read: update to 2.2.2 or later anyway (it's the only version line that even claims to address this), but until Wordfence confirms the fix, also follow the precautions below as if you were still exposed. Believing the vendor costs you nothing here; believing the all-clear too early could cost you a migration.

What To Do Now

  1. Update Prime Mover to 2.2.2 or later. (wp plugin update prime-mover, or Plugins → Update in wp-admin.)
  2. Hold your migrations until you've updated. Don't run an export or restore on the vulnerable version — that's the trigger.
  3. Review recent comments for planted payloads. Look for comments containing long, unbroken base64-looking strings (long runs of A–Z, a–z, 0–9, +, /, ending in =). Delete anything you don't recognize, especially on posts where comments make no sense.
  4. If you migrated recently on the vulnerable version, treat it as worth a closer look: check for admin users and files you don't recognize, and read our guide to checking whether your web app is hacked. If anything looks off, rotate your WordPress salts and admin credentials.
  5. Consider whether you need the plugin at all. Backup and migration plugins run with total access to your site. If you installed Prime Mover for a one-off move months ago, deactivating it between migrations removes the surface entirely.

The Bigger Lesson

This is the second WordPress plugin emergency we've covered this month (the other: php2shell and Bricksforge), and the pattern is the same one that bites vibe-coded and shipped-fast sites everywhere: the tools with the deepest access get the least scrutiny. A migration plugin can read your whole database and write files across your site — that's its job. Treat your plugin list the way you treat your dependency list: inventory it, keep it short, and update it like it matters, because an attacker is reading the same changelog you are.

Run the free mini-scan at preshipit.com/free-scan — paste your URL and see what your site announces to strangers, including a Prime Mover version in the CVE-2026-115806 range if it's disclosing one. The full scan ($29, one-time) goes deeper: active probing, backend-rule checks, and copy-paste fixes for everything it finds.

Check Prime Mover on your own site — free.

Our free WordPress Plugin Vulnerability Checker pulls Prime Mover's current version from wordpress.org and lists the vulnerabilities our scanner checks for — CVE-2026-115806 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 Prime Mover on your site? Check it against CVE-2026-115806 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your Prime Mover is in the affected range (≤ 2.2.1), 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