Dynamic CTR Security & Risk Analysis

wordpress.org/plugins/dynamic-ctr

Simple and lightweight plugin for creating and managing custom taxonomies in WordPress.

0 active installs v1.1 PHP 7.0+ WP 4.7+ Updated Apr 18, 2024
ctrcustomdynamictaxonomytype
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Dynamic CTR Safe to Use in 2026?

Generally Safe

Score 85/100

Dynamic CTR has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 2yr ago
Risk Assessment

Based on the provided static analysis and vulnerability history, the 'dynamic-ctr' plugin v1.1 exhibits a very strong security posture. The absence of any identified AJAX handlers, REST API routes, shortcodes, or cron events with an unprotected attack surface is a significant strength. The code signals also indicate good development practices, with 100% of SQL queries using prepared statements and all output properly escaped. The presence of nonce and capability checks, even with a limited attack surface, further bolsters its security. Furthermore, the complete lack of any recorded vulnerabilities, past or present, suggests a mature and well-maintained plugin.

The analysis reveals no identified taint flows, dangerous functions, file operations, or external HTTP requests, which are all positive indicators. The only item of note is the inclusion of the 'Select2' bundled library, which could potentially be an outdated version if not actively maintained. However, without specific version information or known vulnerabilities associated with bundled libraries, this is a minor point.

In conclusion, 'dynamic-ctr' v1.1 appears to be a highly secure plugin. Its minimal attack surface and adherence to secure coding practices significantly reduce the risk of common web vulnerabilities. The perfect track record of no known CVEs further reinforces this assessment. The primary, albeit minor, area for attention would be ensuring any bundled libraries are kept up-to-date.

Key Concerns

  • Bundled library could be outdated
Vulnerabilities
None known

Dynamic CTR Security Vulnerabilities

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

Dynamic CTR Release Timeline

v1.1Current
Code Analysis
Analyzed Apr 16, 2026

Dynamic CTR Code Analysis

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

Bundled Libraries

Select2

Output Escaping

100% escaped48 total outputs
Attack Surface

Dynamic CTR Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 6
actionadmin_enqueue_scriptsdynamic-ctr.php:33
actioninitinc/create_post.inc.php:28
actionadd_meta_boxesinc/metabox.inc.php:147
actionsave_postinc/metabox.inc.php:148
actioninitinc/register-texonomy.inc.php:57
actioninitinc/register_texonomy_post.inc.php:20
Maintenance & Trust

Dynamic CTR Maintenance & Trust

Maintenance Signals

WordPress version tested6.5.8
Last updatedApr 18, 2024
PHP min version7.0
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

Dynamic CTR Developer Profile

Kazi Mohammad Foysal

7 plugins · 140 total installs

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

How We Detect Dynamic CTR

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/dynamic-ctr/src/lib/select2/css/select2.min.css/wp-content/plugins/dynamic-ctr/src/lib/select2/js/select2.min.js/wp-content/plugins/dynamic-ctr/src/js/select2-init.js

HTML / DOM Fingerprints

Data Attributes
name="kmfdtr_metadata[][tax_name]"name="kmfdtr_metadata[][tax_id]"name="kmfdtr_metadata[][hirarchial]"name="kmfdtr_metadata[][query_var]"name="kmfdtr_metadata[][show_admin_column]"name="kmfdtr_metadata[][post_types]"
FAQ

Frequently Asked Questions about Dynamic CTR