Is Post Cloner safe to use?

Laskyr does not give safety verdicts. The latest version (1.0.0) has 1 known unpatched vulnerability. As of 2026-11-04, the sources we check list the newest release of Post Cloner as affected and name no fixed version yet. Keep Post Cloner on the latest version (1.0.0) and remove it if you do not use it.

Which versions of Post Cloner are vulnerable?

Known issues on record (newest first): Missing authorization check (1.0.0 and older). The full list with sources is on this page.

What is the latest version of Post Cloner?

1.0.0, according to wordpress.org (last updated 2023-12-13). It has 1,000+ active installs.

What should I do if my Post Cloner is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update post-cloner). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · post-cloner · data as of 2026-11-04

Is Post Cloner safe? Known vulnerabilities and latest version

Latest version: 1.0.0
Last updated: 2023-12-13
Active installs: 1,000+
Known issues on record: 1
Unpatched in latest: 1
Tested up to WP: 6.4.14

Post cloner allows you to easily make complete duplicates of any post on your site. That includes posts, pages and custom post types. — by Evan Herman

What to do

There is no fixed version yet. If you can live without Post Cloner for now, deactivate it and delete it until the developer ships a fix.
If you must keep it, limit who can log in (remove unused accounts, especially low-level ones) and put a web application firewall in front of the site.
Watch for an update: get an email when this page changes.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.

With WP-CLI: wp plugin get post-cloner --field=version shows what you run; wp plugin update post-cloner updates it.

Check your version

Known vulnerabilities

1 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 5.3 affects latest 1.0.0 CVE-2025-62865 · published 2025-12-09

Missing authorization check in Post Cloner (1.0.0 and older)

Affected: 1.0.0 and older
Fixed in: no fix listed yet
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Missing Authorization vulnerability in Evan Herman Post Cloner post-cloner allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Post Cloner: from n/a through <= 1.0.0.

NVD CVE-2025-62865 Patchstack advisory

Recent activity

2023-12-13 — latest release on wordpress.org (1.0.0).
2025-12-09 — Missing authorization check disclosed (CVE-2025-62865), no fix listed yet.

Free. We check the CVE feeds every day and email you only when a new issue for Post Cloner (post-cloner) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Missing authorization (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/post-cloner (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/post-cloner"><img src="https://laskyr.com/plugins/post-cloner/badge.svg" alt="Post Cloner vulnerability status"></a>

← Check another plugin · Free hacked-site scan