CVE-2026-14492: WP Duplicate Unauth File Upload RCE - No Patch, Remove It

CVE-2026-14492 is Wordfence Intelligence's name for unauthenticated arbitrary file upload → remote code execution in WP Duplicate - WordPress Migration Plugin, wordpress.org slug local-sync, through 1.1.11. Title on their intel page: WP Duplicate <= 1.1.11 - Unauthenticated Arbitrary File Upload to Remote Code Execution via 'files_data' Parameter in handle_batch_upload_files. Publicly published 18 November 2026, last updated the same day. Finder: Spy0x7. Wordfence CVSS 3.1 9.8 CRITICAL AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Weakness label on that page: Unrestricted Upload of File with Dangerous Type (CWE-434).[1]
Patched? Wordfence: No. Remediation text: no known patch; uninstall and replace.[1]
CVE.org this morning: the ID is RESERVED (CNA JSON 404). NVD: CVE ID Not Found because RESERVED IDs are not ingested. Absence from NVD is not “not a CVE.” The published write-up is the Wordfence intel page.[2][3][4]
It is not in CISA KEV catalog 2026.11.18 (1,786 entries, dateReleased 2026-11-18T19:17:41.0354Z). The four KEV adds that day are Synology DSM CVE-2024-10441, BerriAI LiteLLM CVE-2026-40217, Apache Axis CVE-2026-90436, and REDCap CVE-2026-90817. Different products.[5][6]
wordpress.org: slug local-sync closed as of 9 November 2026, “not available for download,” “closure is temporary, pending a full review.” The plugins.info API returns "closed": true. That closure is nine days before Wordfence published 14492; do not treat the directory page as a patched release.[7]
What it is
Wordfence, not a lab from us: save_single_batch_file (reached via handle_batch_upload_files / files_data) writes a file whose path is built from unsanitized base64-decoded input, with no directory-traversal containment. In front of that sits a PHP type-juggling authentication bypass: a loose != comparison with no is_string() guard. Exploitation, they say, requires the site owner to have finished the plugin's initial setup so site_type and prod_key_random_id are non-empty - and that any non-empty secret is bypassable via the type-juggling flaw.[1]
Read the 14492 body carefully. The title and CVSS are unauthenticated (PR:N). The paragraph also says “authenticated attackers, with custom-level access and above.” We did not resolve that contradiction in a lab. Treat the vector Wordfence published (PR:N) as their score, and treat the setup-options sentence as a precondition they named, not as “you need a WP login.”[1]
The sibling advisory CVE-2026-14491 (same day, same researcher, same slug, same “Patched? No”) is more explicit about the bypass: submit the JSON boolean true as prod_key_random_id, which coerces against any non-empty stored secret so the loose != does not take the reject branch - without knowing the secret. That one is unauthenticated arbitrary file read via file_name, CVSS 7.5. Same Trac file they cite for the comparison (includes/class-local-sync.php around line 221). We are not publishing a request body.[8]
This is not:
- Yesterday's CVE-2026-121684 Soledad theme AJAX LFI. Different product; that one has a floor (8.7.8).
- WordPress core 7.1.4 / CVE-2026-119977 upgrade-window RCE (KEV 3 Nov). Patching core does not remove
local-sync. - CVE-2026-40217 LiteLLM on KEV today. Inference gateway, not this plugin.
- A cPanel / Plesk / LiteSpeed CVE. The control is delete the plugin directory.
Same plugin, already in Wordfence's family: CVE-2026-123751 (9.8 unauth file upload, 6 Nov, Mike Gozdiskowski) and older subscriber+ upload bugs (CVE-2026-39755, CVE-2026-1499). CVE-2026-85776 (subscriber+ RCE via start_zip_creation, 18 Nov) is a third 18 Nov ID. One uninstall covers the tree.[1]
How serious is it?
- Wordfence: unauthenticated file upload to RCE. 9.8. Network, low complexity, no privileges, no user interaction, high C/I/A. That is their number on the intel page, not an NVD rescore - NVD has no row.[1][3]
- No patch. Wordfence's remediation is uninstall. There is no “wait for 1.1.12” sentence in the record we fetched.[1]
- wordpress.org closed 9 Nov, pending review - not a security-issue reason string, and not a new zip.[7]
- KEV: not listed in 2026.11.18. No CISA “evidence of active exploitation” stamp, no ransomware flag, no BOD due date for this ID.[5][6]
- Attack counter: the 14492 intel page we fetched did not show a “blocked N attacks” line. Do not invent one.[1]
- Install count: wordpress.org active-installs is not published on a closed listing. Do not invent “N thousand sites.”[7]
Blast radius on a shared host is each site with wp-content/plugins/local-sync/ still on disk. A webshell as the site user is a tenant incident; it is not automatically host-root unless something else on the box is already broken.
Who is affected
| Product / setup | This bug? | Floor / note |
|---|---|---|
local-sync ≤ 1.1.11 (WP Duplicate - WordPress Migration Plugin) |
Yes, Wordfence | No patched version. Uninstall.[1] |
| Plugin inactive but directory still present | Files can still be hit if WP loads the plugin bootstrap | Delete the tree, do not only deactivate.[1][7] |
Setup never completed (site_type / prod_key_random_id empty) |
Wordfence named those options as a precondition | Do not keep the plugin on that theory. Uninstall anyway.[1] |
local-sync 1.1.12+ |
No such release in the records we fetched | wordpress.org is closed; there is no directory zip to update to.[7] |
| Other “duplicate / migrate / clone” plugins (WP STAGING, Duplicator, All-in-One WP Migration, etc.) | No | Different slugs. This CVE is local-sync only.[1] |
| WordPress core | No | Different code.[1] |
| NVD / CVE.org published record | None as of this morning | CVE.org RESERVED; use Wordfence until the CNA JSON lands.[2][3][4] |
What to do now
- Find the slug, not the marketing name. Dashboard titles say “WP Duplicate.” The directory is
local-sync.
# one site
wp plugin list --name=local-sync --fields=name,status,version --skip-plugins --skip-themes
# cPanel box, every account (read-only) - inactive copies count
find /home -path '*/wp-content/plugins/local-sync' -type d 2>/dev/null
Anything local-sync ≤ 1.1.11 is in Wordfence's range. There is no wordpress.org update channel while the listing is closed.[1][7]
- Deactivate, delete, confirm the directory is gone. There is no vendor floor.
wp plugin deactivate local-sync --skip-themes
wp plugin delete local-sync --skip-themes
test ! -d wp-content/plugins/local-sync && echo gone
If wp is broken, move the directory out of plugins/ as root and chown it off the vhost, then delete after you have a copy for forensics.
-
If you cannot delete this hour: this is not a core file you can hotfix from wordpress.org. Restrict unauthenticated hits to the plugin's PHP under
wp-content/plugins/local-sync/at the WAF only as a stopgap. A WAF rule is not the floor. We are not publishing a payload signature.[1] -
Hunt like a tenant RCE, not like a panel CVE.
# unexpected PHP under uploads (generic webshell pass, not a vendor IoC)
find wp-content/uploads -type f -name '*.php' 2>/dev/null
# leftover plugin tree after a "deactivate"
ls -la wp-content/plugins/local-sync 2>/dev/null || echo absent
Wordfence did not publish a hash or filename for 14492. A PHP file in uploads is suspicious on any WP box; it is not proof of this CVE.
- Shared-hosting operators: inventory every account, not the ones that opened a ticket. Closed plugins do not show up in “can I update?” queues.
# cheap fleet pass on a typical cPanel layout
find /home -path '*/wp-content/plugins/local-sync/local-sync.php' 2>/dev/null
- After the directory is gone: rotate application passwords, reset administrators you did not create, and treat any PHP in
uploadsas a separate incident. Removing the plugin does not evict a shell that is already there. If this site used the plugin as a migrate/clone tool, treatwp-config.phpand DB dumps it may have written as exposed until you prove otherwise - sibling 14491 is unauth file read.[8]
Unsupported versions
Wordfence affected range is ≤ 1.1.11. There is no patched version field. wordpress.org will not auto-update a closed plugin. Automatic updates for plugins is the wrong control.[1][7]
If a customer still “needs” this plugin to finish a migration: finish it on an isolated copy with the plugin off the public vhost, then delete it before DNS/cutover. Do not leave a no-patch migrate plugin on a production URL.
Compromise signs
None of these are vendor IoCs. They are what you look for after any unauth PHP RCE on a WP vhost:
- New administrator in
wp_usersyou did not create. - PHP under
wp-content/uploads/or a modifiedwp-config.php. local-syncstill on disk after you thought you deleted it.- Unexpected files under the plugin directory dated after the last admin login.
A wordpress.org review that mentions Windows Defender quarantining class-local-sync-shell-dump.php is not an IoC for 14492. We are not treating plugin reviews as evidence.[7]
FAQ
Is there a patch? Wordfence says no. Uninstall.[1]
Is it in KEV? No, catalog 2026.11.18, 1,786 rows. Today's KEV adds are Synology / LiteLLM / Axis / REDCap. Do not mix the two queues.[5][6]
CVE.org says RESERVED. Is the ID fake? The ID exists and is RESERVED by a CNA. Wordfence's intel page is already using it. Until cveawg serves a PUBLISHED JSON, cite Wordfence, not NVD.[2][3][4]
Do I need a login? Wordfence scored PR:N and titled it unauthenticated. They also named a completed-setup precondition and, in 14491, a JSON-boolean type-juggle. Do not keep the plugin because “nobody is logged in.”[1][8]
CVSS 9.8 or “high”? Wordfence published 9.8 CRITICAL with AC:L. Nobody we fetched published a lower official score for 14492. CVE.org has no metrics yet.[1][2]
Has it been exploited? Not stated on the intel page we fetched. CISA has not added the CVE to KEV. We did not confirm a named victim.[1][5]
Can I wp plugin update local-sync from wordpress.org? No. The listing is closed as of 9 November 2026.[7]
Honesty
- We did not exploit this. No request body, no
files_datablob, noprod_key_random_idprobe from this box. - CVE.org state is RESERVED. Floor, CVSS, and “no patch” come from Wordfence Intelligence, not from a published CNA JSON or NVD analysis.[1][2][3][4]
- Not in KEV. Not a ransomware-flagged KEV row.[5][6]
- No Wordfence attack counter on the page we fetched 19 Nov. Do not invent one.
- Install counts: unverified (closed directory). Do not invent “N thousand sites.”
- 14492 body vs title on authentication: unresolved. We quoted both.
- Mechanism is Wordfence's paragraph plus the sibling 14491 type-juggle sentence. We did not review a salsa commit.
- Plugin closure 9 Nov is wordpress.org's string (“pending a full review”), not a Wordfence sentence that they closed it for 14492.
Sources
[1] https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/local-sync/wp-duplicate-1111-unauthenticated-arbitrary-file-upload-to-remote-code-execution-via-files-data-parameter-in-handle-batch-upload-files - Wordfence Intelligence, 9.8, no patch, Spy0x7, published 18 Nov 2026
[2] https://www.cve.org/CVERecord?id=CVE-2026-14492 - CVE.org, state RESERVED (fetched 19 Nov 2026)
[3] https://nvd.nist.gov/vuln/detail/CVE-2026-14492 - NVD “CVE ID Not Found” (RESERVED)
[4] https://cveawg.mitre.org/api/cve-id/CVE-2026-14492 - CVE ID API, state RESERVED
[5] https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json - catalog 2026.11.18, 1,786 entries, no CVE-2026-14492
[6] https://www.cisa.gov/news-events/alerts/2026/11/18/cisa-adds-four-known-exploited-vulnerabilities-catalog - KEV adds are CVE-2024-10441, CVE-2026-40217, CVE-2026-90436, CVE-2026-90817
[7] https://wordpress.org/plugins/local-sync/ - closed 9 Nov 2026, pending full review
[8] https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/local-sync/wp-duplicate-1111-unauthenticated-arbitrary-file-read-via-file-name-parameter-via-type-juggling-auth-bypass - CVE-2026-14491, 7.5, same type-juggle, no patch