
Custom Post Types and Custom Fields creator – WCK Security & Risk Analysis
wordpress.org/plugins/wck-custom-fields-and-custom-post-types-creatorA must have tool for creating custom fields, custom post types and taxonomies, fast and without any programming knowledge.
Is Custom Post Types and Custom Fields creator – WCK Safe to Use in 2026?
Generally Safe
Score 100/100Custom Post Types and Custom Fields creator – WCK has a strong security track record. Known vulnerabilities have been patched promptly.
The plugin "wck-custom-fields-and-custom-post-types-creator" v2.3.8 exhibits a mixed security posture. On the positive side, the plugin demonstrates good practices in its use of prepared statements for SQL queries and proper output escaping, with high percentages for both. The presence of nonce and capability checks also indicates an awareness of WordPress security fundamentals. However, a significant concern arises from the presence of two AJAX handlers that lack authentication checks. This creates a direct attack vector for unauthenticated users to interact with potentially sensitive functionality. While no critical or high severity taint flows were identified, the six flows with unsanitized paths are concerning and could be a precursor to vulnerabilities if not carefully managed. The plugin's vulnerability history shows one medium-severity Cross-Site Scripting (XSS) vulnerability, last patched in late 2022, suggesting a past weakness that, while addressed, warrants attention regarding the maintainers' ability to prevent such issues.
Overall, the plugin has strengths in its handling of database operations and output, but the unprotected AJAX endpoints represent a clear and immediate risk. The past XSS vulnerability and unsanitized taint flows, though not currently critical, suggest that diligent security reviews and robust input validation are crucial for this plugin. The absence of critical or high severity issues in the static analysis is reassuring, but the identified weaknesses should not be overlooked, especially concerning the direct exposure of AJAX endpoints.
Key Concerns
- Unprotected AJAX handlers
- Flows with unsanitized paths detected
- Past medium severity XSS vulnerability
Custom Post Types and Custom Fields creator – WCK Security Vulnerabilities
CVEs by Year
Severity Breakdown
1 total CVE
Custom Post Types and Custom Fields creator <= 2.3.2 - Authenticated (Administrator+) Stored Cross-Site Scripting
Custom Post Types and Custom Fields creator – WCK Code Analysis
SQL Query Safety
Output Escaping
Data Flow Analysis
Custom Post Types and Custom Fields creator – WCK Attack Surface
AJAX Handlers 2
WordPress Hooks 133
Maintenance & Trust
Custom Post Types and Custom Fields creator – WCK Maintenance & Trust
Maintenance Signals
Community Trust
Custom Post Types and Custom Fields creator – WCK Alternatives
Meta Box
meta-box
Meta Box plugin is a powerful, professional developer toolkit to create custom meta boxes and custom fields for your custom post types in WordPress.
Pods – Custom Content Types and Fields
pods
Pods is a framework for creating, managing, and deploying customized content types and fields for any project.
Sydney Toolbox
sydney-toolbox
Registers custom post types and custom fields for the Sydney theme
CubeWP Framework
cubewp-framework
CubeWP is an end-to-end dynamic content framework for WordPress to help you shrink time and cut cost of development up to 90%.
Athemes Toolbox
athemes-toolbox
Registers custom post types and custom fields for the aThemes theme
Custom Post Types and Custom Fields creator – WCK Developer Profile
3 plugins · 14K total installs
How We Detect Custom Post Types and Custom Fields creator – WCK
Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.
Asset Fingerprints
/wp-content/plugins/wck-custom-fields-and-custom-post-types-creator/images/wck-menu-item.pngHTML / DOM Fingerprints
wck_meta_box_titledata-plugin-slugdata-field-typedata-field-namewck_settingswck_meta_boxeswck_metabox_args[wck_frontend_form][wck_frontend_edit_form][wck_frontend_display_form]