← All security briefings

Attention

WP Duplicate migration plugin: unauthenticated file read and subscriber-to-administrator sync hijack, no known patch

Identifiers: CVE-2026-14491 · CVE-2026-85776

Published
Last substantive change
Last verified

Last verified: . Attention items are due for re-verification within 72 hours.

Summary

Wordfence published two records on 18 November 2026 for WP Duplicate – WordPress Migration Plugin up to 1.1.11. CVE-2026-14491 lets an unauthenticated attacker read arbitrary server files via the file_name parameter, because a loose comparison on the stored secret can be bypassed without knowing it. CVE-2026-85776 is missing authorization on several AJAX actions, letting a Subscriber-level user rewrite the plugin's prod_site_url setting to an attacker-controlled host and enumerate server directories. Code execution happens only if an administrator later triggers a sync: the site then fetches an unsigned attacker-supplied ZIP and extracts it through a bridge under the web root that works independently of WordPress.

Classification reason: Not established: the Wordfence records published 18 November 2026 describe both issues without reporting observed attacks.

Impact

Disclosure of sensitive files such as configuration without login, and remote code execution after a subsequent administrator-triggered sync.

Who is affected

WordPress sites with WP Duplicate (plugin slug local-sync) 1.1.11 or earlier installed, whether or not migration is in active use. No fixed version is known; the vendor readme and the CNA record both returned 404 when checked on 19 November 2026.

Products and versions

Products and versionsAffectedFixed
WP Duplicate – WordPress Migration Plugin <=1.1.11 for both selected CVEs No known patch in the reviewed Wordfence records; vendor readme endpoint unavailable (404)

Exploitation evidence

Exploitation not established. No established exploitation. The file read needs no login; code execution requires a subscriber account plus a later administrator-triggered sync.

Sources: Wordfence Intelligence

Actions

  1. Identify sites with the plugin and, as Wordfence advises, assess uninstalling it and choosing a replacement. Test the removal and replacement on a staging copy first, then make a controlled, planned change on production. A successful staging test does not by itself prove production is safe.
  2. Before removal, securely preserve any migration or backup artefacts you still need and check whether a legitimate sync is pending.
  3. Do not assume that deactivating the plugin removes a WordPress-independent bridge that may already exist under the web root. The Wordfence record describes that bridge as part of the attack chain, not as something present on every installation, so an administrator should check the web root for such a bridge or other unexpected files and clean up as needed.
  4. Watch for a vendor release and re-check the plugin page before relying on any update.

Unknowns

  • No patched version appears in the reviewed records.
  • No exploitation in the wild or evidence of compromise has been established.
  • We do not name a replacement plugin; suitability depends on your migration needs.

Sources

  • Wordfence Intelligence · retrieved 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
  • Wordfence Intelligence · retrieved https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/local-sync/wp-duplicate-1111-missing-authorization-to-authenticated-subscriber-remote-code-execution-via-start-zip-creation-ajax-action

Change history

  1. — Published: Published 19 November 2026. Wordfence published both records (CVE-2026-14491 and CVE-2026-85776) on 18 November 2026; no vendor fix was identified as of 19 November 2026.

Subscribe: RSS feed · JSON Feed · Feed format and fields