WP Duplicate ≤ 1.1.11: Unauthenticated File Upload to RCE (CVE-2026-123751, CVSS 9.8*)

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

WP Duplicate ≤ 1.1.11: Unauthenticated File Upload to RCE (CVE-2026-123751, CVSS 9.8*)

A duplication helper is supposed to copy what you already have. In the WP Duplicate plugin for WordPress, at version 1.1.11 and below, anyone on the internet can use it to write a file of their choosing onto your server instead. That is CVE-2026-123751: the plugin does not properly verify a request authentication value and does not validate the path or type of uploaded files, making it possible for unauthenticated attackers to write arbitrary files to the server and achieve remote code execution. There is no fixed version named in the CVE record yet — and two statements in that record about exploitation disagree with each other, which we carry plainly below rather than smoothing over.

What Happened

CVE-2026-123751 is an unauthenticated arbitrary file upload vulnerability (CWE-434, Unrestricted Upload of File with Dangerous Type) in the WP Duplicate WordPress plugin, disclosed November 9, 2026 (CNA: WPScan; GitHub Advisory Database record GHSA-v9cp-82qp-rrj6).

Am I Affected?

Check wp-admin → Plugins for a plugin named WP Duplicate and its version. At 1.1.11 or below, you are in the affected range: an unauthenticated visitor can write arbitrary files to your server.

One honesty note, because it is the whole point of how we cover these: our scanner does not claim a version check for this one. The CVE record names no wordpress.org listing or slug for this plugin, and no listing was verified — so no slug is asserted and no install count is quoted here. Keying a readme check to a guessed slug would produce claims we cannot stand behind in either direction. This article exists because the flaw is real and urgent — not because we can detect it passively. What the free mini-scan can do is check the rest of your site's exposed surface while you handle this one by hand.

What To Do Now

  1. Deactivate or remove the plugin until the vendor publishes a release naming this CVE. There is no patched version to update to yet. An upload endpoint that is not running cannot write anything.
  2. Audit your uploads directories and recently modified PHP files. Arbitrary file write leaves files: look for PHP files you did not put there, especially in upload and cache directories, and for files whose modification times you cannot explain.
  3. Audit administrator accounts. Users → All Users: every Administrator should be a person you can name. A file-write flaw is exactly the kind that gets quietly converted into persistent access.
  4. If the plugin is business-critical, restrict it behind authentication at the server level until a fix is named. That is a containment measure, not a fix — the plan should still end with a vendor release that names CVE-2026-123751, or removal.

The Bigger Lesson

An upload endpoint that trusts a request-supplied authentication value instead of the session is an auth bypass wearing a file-upload costume — and an upload that skips path and type validation on top of it hands the attacker both the door and the destination. Both checks belong server-side, on every request: verify who is calling from state the caller cannot forge, then decide what may be written, where, from an allow-list the caller does not control. If any plugin on your site accepts files, those are the two questions worth asking about it today.

Related: WordPress Hardening for AI-Built Sites — the standing version of this discipline. How to Check If Your Web App Is Hacked — the follow-up pass if the audit finds a stranger.


Running WP Duplicate at 1.1.11 or below? Deactivate it until a patched release names this CVE, then run the free check at preshipit.com/free-scan — it covers the exposures a scan can see, and articles like this one cover the ones it can't.

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.

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. 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