CVE-2026-85776 in WP Duplicate Plugin
Summary
by MITRE • 11/19/2026
The WP Duplicate – WordPress Migration Plugin plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 1.1.11. This is due to a missing capability check and missing nonce check on the start_zip_creation, start_zip_download, local_sync_get_init_root_files, and local_sync_get_files_by_key AJAX actions in the start_zip_creation_dev() and sibling functions. This makes it possible for authenticated attackers, with subscriber-level access and above, to overwrite the plugin's prod_site_url setting so it points at an attacker-controlled host and enumerate arbitrary server directories, which when combined with a subsequent administrator-triggered sync results in an unsigned attacker-supplied ZIP archive being fetched, extracted via a WordPress-independent bridge deployed under the web root, resulting in remote code execution on the affected site.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 11/19/2026
The vulnerability identified in WP Duplicate – WordPress Migration Plugin versions up to and including 1.1.11 represents a critical failure in access control mechanisms within the plugin's AJAX handling logic. Specifically, the functions responsible for initiating ZIP archive creation, downloading those archives, and retrieving local synchronization files lack necessary capability checks and nonce verification. This absence of security controls means that any authenticated user with subscriber-level permissions or higher can interact directly with these endpoints without proper authorization validation. The core technical flaw lies in the start_zip_creation_dev() function and its sibling functions, which fail to verify if the requesting user has administrative privileges before allowing operations that manipulate critical plugin settings and file system interactions.
This lack of authorization enforcement allows an attacker to exploit the misconfiguration by overwriting the prod_site_url setting within the plugin's configuration. By redirecting this URL to a host controlled by the attacker, the victim site is coerced into trusting malicious infrastructure during synchronization processes. Furthermore, the vulnerability enables directory enumeration on the server hosting the WordPress installation. Through the local_sync_get_init_root_files and local_sync_get_files_by_key actions, an authenticated attacker can probe the file system structure, identifying sensitive files and directories that may contain credentials or other valuable data for further exploitation attempts.
The operational impact escalates significantly when this vulnerability is combined with a subsequent action triggered by an administrator. If an administrator initiates a sync operation after the prod_site_url has been manipulated, the plugin will fetch an unsigned ZIP archive from the attacker-controlled server. This archive is then extracted via a WordPress-independent bridge deployed under the web root of the target site. Because the content originates from an untrusted source and lacks integrity verification during extraction, it allows for remote code execution on the affected website. The attacker gains full control over the server environment by executing arbitrary PHP scripts or other malicious payloads contained within the extracted archive.
From a classification perspective, this vulnerability aligns with CWE-284 Improper Access Control due to the failure to enforce proper authorization checks before performing sensitive operations. Additionally, it relates to CWE-352 Cross-Site Request Forgery since the lack of nonce verification allows actions to be performed without valid user intent confirmation. In terms of attack vectors, this scenario maps to MITRE ATT&CK techniques such as T1078 Valid Accounts for initial access using low-level credentials and T1505 Server Software Component for deploying malicious bridges or scripts on the server. The exploitation chain also reflects aspects of T1496 Remote File Inclusion if the extracted files are subsequently included, though direct execution via extraction is more prevalent here.
Mitigation strategies should prioritize immediate updates to version 1.1.12 or later where these authorization and nonce checks have been implemented by the developers. Until an update is available, site administrators should restrict user roles that can interact with migration-related features, ensuring only trusted administrative accounts retain access to synchronization tools. Implementing Web Application Firewalls (WAF) rules to monitor for unusual AJAX requests targeting zip creation or file retrieval endpoints can provide a temporary layer of defense. Additionally, enforcing strict output controls and validating all external inputs during archive extraction processes would help mitigate the risk of remote code execution even if an attacker manages to manipulate configuration settings. Regular auditing of plugin permissions and disabling unused features are also recommended best practices to reduce the attack surface associated with third-party WordPress extensions.