Query Filter Security & Risk Analysis

wordpress.org/plugins/query-filter

Advanced taxonomy and Custom Fields CPT filtering plugin.

100 active installs v0.0.2 PHP + WP 3.0.0+ Updated Jul 25, 2015
advancedfilterquerysearchwp-query
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Query Filter Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 10yr ago
Risk Assessment

The 'query-filter' plugin, version 0.0.2, presents a significant security risk due to its unprotected AJAX handlers. The static analysis reveals four AJAX entry points, all of which lack any authentication or authorization checks. This means any unauthenticated user could potentially trigger these handlers, leading to unintended actions or information disclosure. Furthermore, the plugin exhibits a complete lack of output escaping for all 12 identified outputs, making it highly susceptible to Cross-Site Scripting (XSS) vulnerabilities. While the plugin doesn't use dangerous functions or perform raw SQL queries, and has no recorded vulnerability history, these strengths are overshadowed by the critical flaws in its input handling and output sanitization. The absence of nonce and capability checks on AJAX actions, combined with the lack of output escaping, creates a dangerous attack surface.

Key Concerns

  • AJAX handlers without authentication checks
  • No output escaping for any output
  • No nonce checks on AJAX actions
  • No capability checks on AJAX actions
Vulnerabilities
None known

Query Filter Security Vulnerabilities

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

Query Filter Code Analysis

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

Output Escaping

0% escaped12 total outputs
Attack Surface
4 unprotected

Query Filter Attack Surface

Entry Points4
Unprotected4

AJAX Handlers 4

noprivwp_ajax_sidebar_query_filterj-query-filter.php:47
authwp_ajax_sidebar_query_filterj-query-filter.php:48
noprivwp_ajax_sidebar_query_filtertrunk\j-query-filter.php:47
authwp_ajax_sidebar_query_filtertrunk\j-query-filter.php:48
WordPress Hooks 8
actionwidgets_initj-query-filter.php:27
actionwp_register_sidebar_widgetj-query-filter.php:31
actionwp_enqueue_scriptsj-query-filter.php:46
actionpre_get_postsj-query-filter.php:133
actionwidgets_inittrunk\j-query-filter.php:27
actionwp_register_sidebar_widgettrunk\j-query-filter.php:31
actionwp_enqueue_scriptstrunk\j-query-filter.php:46
actionpre_get_poststrunk\j-query-filter.php:133
Maintenance & Trust

Query Filter Maintenance & Trust

Maintenance Signals

WordPress version tested4.3.34
Last updatedJul 25, 2015
PHP min version
Downloads2K

Community Trust

Rating20/100
Number of ratings1
Active installs100
Developer Profile

Query Filter Developer Profile

marsjaninzmarsa

1 plugin · 100 total installs

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

How We Detect Query Filter

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/query-filter/js/jquery.deserialize.js/wp-content/plugins/query-filter/js/purl.js/wp-content/plugins/query-filter/js/j-query-filter.js
Script Paths
/wp-content/plugins/query-filter/js/j-query-filter.js
Version Parameters
query-filter/js/j-query-filter.js?ver=query-filter/css/

HTML / DOM Fingerprints

CSS Classes
eotnoResults
Data Attributes
data-lp
JS Globals
J_QUERY_FILTER_V
Shortcode Output
<div hidden data-lp=<div hidden class="eot"></div><div class="noResults">
FAQ

Frequently Asked Questions about Query Filter