HomeWordPress vulnerabilitiesPost Duplicator
Post Duplicator vulnerabilities
Post Duplicator has 6 known vulnerabilities in this database. The most recent published record is dated 22 Aug 2026.
- Known vulnerabilities
- 6
- Active installs
- 200,000+
- Latest version
- 3.0.16
- Last updated
- 22 Aug 2026
- Most recent
- 22 Aug 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Broken access control CVE-2026-4244 | Medium 4.3 | Up to 3.0.11 | Fixed in a later version (latest 3.0.16) | 22 Aug 2026 |
| Broken access control CVE-2026-4245 | Medium 4.3 | Up to 3.0.11 | Fixed in a later version (latest 3.0.16) | 22 Aug 2026 |
| Security weakness CVE-2026-10749 | High 7.2 | Before 3.0.15 | Fixed in 3.0.15 | 24 Jun 2026 |
| Broken access control CVE-2026-2301 | Medium 4.3 | Up to 3.0.8 | Fixed in a later version (latest 3.0.16) | 25 Feb 2026 |
| Broken access control CVE-2024-12472 | Medium 4.3 | Before 2.37 | Fixed in 2.37 | 11 Jan 2025 |
| Cross-site scripting (XSS) CVE-2016-15027 | Low 3.5 | Not yet published | Check for an update | 20 Feb 2023 |
Read the published descriptions
- CVE-2026-4244, 22 Aug 2026
- The Post Duplicator plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the `duplicate_post()` function in all versions up to, and including, 3.0.11. This is due to the function not verifying that the user has `edit_others_posts` capability before accepting a `selectedAuthorId` parameter via the `duplicate-post` REST endpoint. This makes it possible for authenticated attackers, with Contributor-level access and above, to create duplicated posts attributed to any user, including administrators. CVE record
- CVE-2026-4245, 22 Aug 2026
- The Post Duplicator plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 3.0.11. This is due to the `duplicate_post_permissions()` permission callback only verifying the `duplicate_posts` capability without checking whether the requesting user holds `publish_posts` or other status-gated capabilities. This makes it possible for authenticated attackers, with Contributor-level access and above, to create duplicate posts with `future` (scheduled, auto-publishes) or `private` status, bypassing editorial review. Additionally, the REST endpoint does not enforce administrator-configured post-type duplication restrictions, allowing duplication of post types that have been explicitly disabled. CVE record
- CVE-2026-10749, 24 Jun 2026
- The Post Duplicator WordPress plugin before 3.0.15 does not safely handle custom meta-data during post duplication, storing attacker-supplied serialized values without the WordPress meta API's double-serialization protection, allowing users with Contributor-level access and above to inject a PHP Object. CVE record
- CVE-2026-2301, 25 Feb 2026
- The Post Duplicator plugin for WordPress is vulnerable to unauthorized arbitrary protected post meta insertion in all versions up to, and including, 3.0.8. This is due to the `duplicate_post()` function in `includes/api.php` using `$wpdb->insert()` directly to the `wp_postmeta` table instead of WordPress's standard `add_post_meta()` function, which would call `is_protected_meta()` to prevent lower-privileged users from setting protected meta keys (those starting with `_`). This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary protected post meta keys such as `_wp_page_template`, `_wp_attached_file`, and other sensitive meta keys on duplicated posts via the `customMetaData` JSON array parameter in the `/wp-json/post-duplicator/v1/duplicate-post` REST API endpoint. CVE record
- CVE-2024-12472, 11 Jan 2025
- The Post Duplicator plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 2.36 via the mtphr_duplicate_post() function due to insufficient restrictions on which posts can be duplicated. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract data from password protected, private, or draft posts that they should not have access to by duplicating the post. CVE record
- CVE-2016-15027, 20 Feb 2023
- A vulnerability was found in meta4creations Post Duplicator Plugin 2.18 on WordPress. It has been classified as problematic. Affected is the function mtphr_post_duplicator_notice of the file includes/notices.php. The manipulation of the argument post-duplicated leads to cross site scripting. It is possible to launch the attack remotely. Upgrading to version 2.19 is able to address this issue. The name of the patch is ca67c05e490c0cf93a1e9b2d93bfeff3dd96f594. It is recommended to upgrade the affected component. The identifier of this vulnerability is VDB-221496. CVE record
What to do if you run Post Duplicator
If you run Post Duplicator, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Post Duplicator vulnerabilities
Free. We email you when a new vulnerability is published for Post Duplicator, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.