Kntnt's Any Term for Beaver Builder Page Builder Security & Risk Analysis

wordpress.org/plugins/kntnts-bb-any-term

WordPress plugin that adds special purpose term to every taxonomy (including categories and tags) that makes taxonomy filters in post modules of Beave …

10 active installs v1.0.4 PHP 7.0+ WP 4.6+ Updated Apr 12, 2018
beaver-buildercategoryrelated-poststagstaxonomy
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Kntnt's Any Term for Beaver Builder Page Builder Safe to Use in 2026?

Generally Safe

Score 85/100

Kntnt's Any Term for Beaver Builder Page Builder has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 7yr ago
Risk Assessment

Based on the provided static analysis and vulnerability history, the 'kntnts-bb-any-term' plugin version 1.0.4 exhibits a strong security posture. The code analysis reveals no detected dangerous functions, no unescaped outputs, and all SQL queries are properly prepared. Furthermore, there are no file operations or external HTTP requests, and importantly, no identified vulnerability history, including known CVEs. The complete absence of AJAX handlers, REST API routes, shortcodes, and cron events significantly limits the plugin's attack surface, and the zero unprotected entry points further bolster its security. This indicates a conscientious approach to development with a focus on secure coding practices. The lack of any recorded vulnerabilities over time is a positive indicator of ongoing security awareness. While the plugin appears very secure in its current state, the primary observation is the minimal functionality exposed, which naturally reduces the potential for vulnerabilities. The absence of certain security checks like nonces and capabilities is understandable given the lack of exposed entry points that would typically require them. Overall, the plugin is assessed as highly secure.

Vulnerabilities
None known

Kntnt's Any Term for Beaver Builder Page Builder Security Vulnerabilities

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

Kntnt's Any Term for Beaver Builder Page Builder Code Analysis

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

Kntnt's Any Term for Beaver Builder Page Builder Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 10
actioninitkntnt-bb-any-term.php:45
actionfl_ajax_before_render_module_settingskntnt-bb-any-term.php:49
actionfl_ajax_after_render_module_settingskntnt-bb-any-term.php:50
actionfl_ajax_before_get_autosuggest_valueskntnt-bb-any-term.php:52
actionfl_ajax_after_get_autosuggest_valueskntnt-bb-any-term.php:53
actionfl_ajax_before_fl_builder_autosuggestkntnt-bb-any-term.php:57
actionfl_ajax_after_fl_builder_autosuggestkntnt-bb-any-term.php:58
filterget_termskntnt-bb-any-term.php:61
filterfl_builder_loop_before_query_settingskntnt-bb-any-term.php:64
actionpre_get_postskntnt-bb-any-term.php:67
Maintenance & Trust

Kntnt's Any Term for Beaver Builder Page Builder Maintenance & Trust

Maintenance Signals

WordPress version tested4.9.29
Last updatedApr 12, 2018
PHP min version7.0
Downloads3K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Kntnt's Any Term for Beaver Builder Page Builder Developer Profile

Thomas Barregren

2 plugins · 10 total installs

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

How We Detect Kntnt's Any Term for Beaver Builder Page Builder

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

Asset Fingerprints

Version Parameters
kntnt-bb-any-term/kntnt-bb-any-term.php?ver=

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Kntnt's Any Term for Beaver Builder Page Builder