Clone My Post Security & Risk Analysis

wordpress.org/plugins/clone-my-post

Clone/Duplicate Posts, Pages with a single click

0 active installs v1.0.1 PHP 7.4+ WP 6.0+ Updated Jun 17, 2025
clone-postcontent-duplicatecopy-pageduplicate-postwordpress-post-duplicate
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Clone My Post Safe to Use in 2026?

Generally Safe

Score 100/100

Clone My Post has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 11mo ago
Risk Assessment

The "clone-my-post" v1.0.1 plugin exhibits a strong security posture based on the provided static analysis. It demonstrates excellent adherence to secure coding practices, with all identified SQL queries using prepared statements and all output being properly escaped. The absence of file operations and external HTTP requests further reduces the potential attack surface. Crucially, all detected AJAX handlers include nonce checks and capability checks, indicating robust authentication and authorization mechanisms for its single entry point.

The taint analysis revealed no flows with unsanitized paths, and the vulnerability history is completely clean, with no recorded CVEs. This lack of past vulnerabilities and the absence of any critical or high-severity issues in the current code analysis suggest a well-maintained and secure plugin. The plugin's strengths lie in its diligent implementation of WordPress security best practices for input validation, output sanitization, and access control.

While the plugin appears very secure, the analysis is limited to the provided data. The sole AJAX handler, though protected, represents a single point of interaction that could theoretically be a target if future vulnerabilities are introduced. However, based on the current evidence, the risk associated with this plugin is very low.

Vulnerabilities
None known

Clone My Post Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Version History

Clone My Post Release Timeline

v1.0.1Current
Code Analysis
Analyzed Apr 16, 2026

Clone My Post Code Analysis

Dangerous Functions
0
Raw SQL Queries
0
0 prepared
Unescaped Output
0
87 escaped
Nonce Checks
4
Capability Checks
8
File Operations
0
External Requests
0
Bundled Libraries
0

Output Escaping

100% escaped87 total outputs
Data Flows · Security
All sanitized

Data Flow Analysis

3 flows
bssclmyp_clone_my_post_as_draft (clone-my-post.php:111)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Clone My Post Attack Surface

Entry Points1
Unprotected0

AJAX Handlers 1

authwp_ajax_bssclmyp_mk_dp_close_dp_helpclone-my-post.php:50
WordPress Hooks 10
actionadmin_menuclone-my-post.php:33
filterplugin_action_linksclone-my-post.php:34
actionadmin_action_bssclmyp_clone_my_post_as_draftclone-my-post.php:35
filterpost_row_actionsclone-my-post.php:38
filterpage_row_actionsclone-my-post.php:39
actionadmin_headclone-my-post.php:41
actionadmin_headclone-my-post.php:43
actionpost_submitbox_misc_actionsclone-my-post.php:44
actionpost_submitbox_misc_actionsclone-my-post.php:46
actionwp_before_admin_bar_renderclone-my-post.php:48
Maintenance & Trust

Clone My Post Maintenance & Trust

Maintenance Signals

WordPress version tested6.8.5
Last updatedJun 17, 2025
PHP min version7.4
Downloads288

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

Clone My Post Developer Profile

Bss

3 plugins · 0 total installs

91
trust score
Avg Security Score
95/100
Avg Patch Time
30 days
View full developer profile
Detection Fingerprints

How We Detect Clone My Post

Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.

Asset Fingerprints

Asset Paths
/wp-content/plugins/clone-my-post/include/admin-settings.php
Version Parameters
clone-my-post/style.css?ver=

HTML / DOM Fingerprints

Data Attributes
data-post-id
FAQ

Frequently Asked Questions about Clone My Post