Custom Post Type Editor Security & Risk Analysis

wordpress.org/plugins/cpt-editor

Customize the text labels, menu names or description for any registered custom post type using a simple Dashboard user interface.

2K active installs v1.6.1 PHP + WP 6.0+ Updated Jul 17, 2024
cptcustom-post-typedescriptionlabelpost-type
92
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Custom Post Type Editor Safe to Use in 2026?

Generally Safe

Score 92/100

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

No known CVEs Updated 1yr ago
Risk Assessment

The cpt-editor v1.6.1 plugin exhibits a strong security posture based on the provided static analysis. The complete absence of AJAX handlers, REST API routes, shortcodes, and cron events with unprotected entry points significantly minimizes the attack surface. The code demonstrates excellent practices with 100% of SQL queries using prepared statements and a high rate (94%) of properly escaped output. The presence of nonce and capability checks further bolsters its security.

The taint analysis shows no flows with unsanitized paths or critical/high severity issues, indicating robust data handling within the analyzed code. The plugin's vulnerability history is clean, with no recorded CVEs, which suggests a consistent focus on security by the developers. This lack of past vulnerabilities further reinforces the current positive security assessment.

Overall, the cpt-editor v1.6.1 appears to be a secure plugin with excellent defensive coding practices and a minimal attack surface. The limited scope of its functionality, as suggested by the analysis, likely contributes to this strong security profile. There are no immediate, evidence-backed security concerns identified in this data.

Vulnerabilities
None known

Custom Post Type Editor Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Code Analysis
Analyzed Mar 16, 2026

Custom Post Type Editor Code Analysis

Dangerous Functions
0
Raw SQL Queries
0
0 prepared
Unescaped Output
2
31 escaped
Nonce Checks
1
Capability Checks
1
File Operations
0
External Requests
0
Bundled Libraries
0

Output Escaping

94% escaped33 total outputs
Data Flows
All sanitized

Data Flow Analysis

2 flows
admin_page_edit (cpt-editor.php:379)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Custom Post Type Editor Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 4
actionplugins_loadedcpt-editor.php:115
actioninitcpt-editor.php:117
actionadmin_menucpt-editor.php:119
actionregistered_post_typecpt-editor.php:129
Maintenance & Trust

Custom Post Type Editor Maintenance & Trust

Maintenance Signals

WordPress version tested6.6.5
Last updatedJul 17, 2024
PHP min version
Downloads70K

Community Trust

Rating98/100
Number of ratings14
Active installs2K
Developer Profile

Custom Post Type Editor Developer Profile

Tectalic

5 plugins · 15K total installs

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

How We Detect Custom Post Type Editor

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/cpt-editor/css/cpt-editor.css/wp-content/plugins/cpt-editor/js/cpt-editor.js
Version Parameters
/wp-content/plugins/cpt-editor/css/cpt-editor.css?ver=/wp-content/plugins/cpt-editor/js/cpt-editor.js?ver=

HTML / DOM Fingerprints

CSS Classes
cpt-editor-wrap
Data Attributes
data-cpt-editor-field
JS Globals
OM4_CPT_Editor_AdmincptEditorAdmin
FAQ

Frequently Asked Questions about Custom Post Type Editor