Rich Taxonomy Security & Risk Analysis

wordpress.org/plugins/rich-taxonomy

A WordPress plugin that enhances taxonomy archives by replacing them with custom Taxonomy Pages. > Note: This plugin works with both classic them …

10 active installs v1.2.1 PHP 7.0+ WP 5.9+ Updated Jan 19, 2026
seotaxonomyterms
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Rich Taxonomy Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs Updated 2mo ago
Risk Assessment

The "rich-taxonomy" plugin v1.2.1 demonstrates a strong security posture based on the provided static analysis. The plugin has no identified attack surface through AJAX, REST API, shortcodes, or cron events. Furthermore, the code shows excellent practices with no dangerous functions, 100% SQL query preparation, and 100% output escaping. The presence of nonce checks and capability checks on core operations further enhances its security. The plugin also has a clean vulnerability history with no recorded CVEs, which suggests a history of secure development or a lack of significant security incidents.

While the static analysis reveals no immediate critical vulnerabilities, the presence of a file operation and a single file operation without further context could be a potential area for concern if not handled securely. However, the limited attack surface and robust code hygiene mitigate this risk significantly. Given the absence of identified taint flows and a clean vulnerability history, the overall risk associated with "rich-taxonomy" v1.2.1 is very low. The plugin is well-coded and appears to be developed with security in mind.

Key Concerns

  • Single file operation identified
Vulnerabilities
None known

Rich Taxonomy Security Vulnerabilities

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

Rich Taxonomy Code Analysis

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

Output Escaping

100% escaped29 total outputs
Attack Surface

Rich Taxonomy Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 35
actionplugins_loadedrich-taxonomy.php:34
actioninitsrc\Tarosky\RichTaxonomy\Bootstrap.php:44
actionenqueue_block_editor_assetssrc\Tarosky\RichTaxonomy\Bootstrap.php:46
filterget_the_excerptsrc\Tarosky\RichTaxonomy\Controller\DataSync.php:24
actiondelete_termsrc\Tarosky\RichTaxonomy\Controller\DataSync.php:26
filtertag_row_actionssrc\Tarosky\RichTaxonomy\Controller\Editor.php:27
actionadmin_enqueue_scriptssrc\Tarosky\RichTaxonomy\Controller\Editor.php:29
actioninitsrc\Tarosky\RichTaxonomy\Controller\Editor.php:31
filterpost_row_actionssrc\Tarosky\RichTaxonomy\Controller\Editor.php:35
actionadmin_headsrc\Tarosky\RichTaxonomy\Controller\Editor.php:37
actionadd_meta_boxessrc\Tarosky\RichTaxonomy\Controller\Editor.php:44
actionenqueue_block_editor_assetssrc\Tarosky\RichTaxonomy\Controller\Editor.php:46
actionadmin_noticessrc\Tarosky\RichTaxonomy\Controller\Editor.php:48
filterposts_resultssrc\Tarosky\RichTaxonomy\Controller\Rewrites.php:27
actiontemplate_redirectsrc\Tarosky\RichTaxonomy\Controller\Rewrites.php:29
filtersingle_term_titlesrc\Tarosky\RichTaxonomy\Controller\Rewrites.php:31
filtersingle_tag_titlesrc\Tarosky\RichTaxonomy\Controller\Rewrites.php:32
filtersingle_cat_titlesrc\Tarosky\RichTaxonomy\Controller\Rewrites.php:33
filterpost_type_linksrc\Tarosky\RichTaxonomy\Controller\Rewrites.php:35
filtertemplate_includesrc\Tarosky\RichTaxonomy\Controller\Rewrites.php:46
filtertag_templatesrc\Tarosky\RichTaxonomy\Controller\Rewrites.php:50
filtercategory_templatesrc\Tarosky\RichTaxonomy\Controller\Rewrites.php:51
filtertaxonomy_templatesrc\Tarosky\RichTaxonomy\Controller\Rewrites.php:52
filtersingle_templatesrc\Tarosky\RichTaxonomy\Controller\Rewrites.php:54
filtersingular_templatesrc\Tarosky\RichTaxonomy\Controller\Rewrites.php:55
actionadmin_initsrc\Tarosky\RichTaxonomy\Controller\Setting.php:35
actionadmin_noticessrc\Tarosky\RichTaxonomy\Controller\Setting.php:36
actionsave_postsrc\Tarosky\RichTaxonomy\Controller\Templates.php:26
actionadd_meta_boxessrc\Tarosky\RichTaxonomy\Controller\Templates.php:27
actionplugins_loadedsrc\Tarosky\RichTaxonomy\Pattern\AbstractVendor.php:31
actioninitsrc\Tarosky\RichTaxonomy\Pattern\BlockPattern.php:38
actionenqueue_block_editor_assetssrc\Tarosky\RichTaxonomy\Pattern\BlockPattern.php:39
actionrest_api_initsrc\Tarosky\RichTaxonomy\Pattern\RestApiPattern.php:31
filtertcs_style_groupssrc\Tarosky\RichTaxonomy\Vendor\TaroCustomStyle.php:30
filtertcs_object_for_stylesrc\Tarosky\RichTaxonomy\Vendor\TaroCustomStyle.php:31
Maintenance & Trust

Rich Taxonomy Maintenance & Trust

Maintenance Signals

WordPress version tested6.8.5
Last updatedJan 19, 2026
PHP min version7.0
Downloads8K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Rich Taxonomy Developer Profile

TAROSKY INC.

12 plugins · 680 total installs

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

How We Detect Rich Taxonomy

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/rich-taxonomy/assets/css/editor.css/wp-content/plugins/rich-taxonomy/assets/js/editor.js/wp-content/plugins/rich-taxonomy/assets/js/term-list.js
Script Paths
/wp-content/plugins/rich-taxonomy/assets/js/editor.js/wp-content/plugins/rich-taxonomy/assets/js/term-list.js
Version Parameters
/wp-content/plugins/rich-taxonomy/assets/css/editor.css?ver=/wp-content/plugins/rich-taxonomy/assets/js/editor.js?ver=/wp-content/plugins/rich-taxonomy/assets/js/term-list.js?ver=

HTML / DOM Fingerprints

CSS Classes
rich-taxonomy-link
Data Attributes
data-term_id
JS Globals
richTaxonomy
FAQ

Frequently Asked Questions about Rich Taxonomy