Persistent Filters Security & Risk Analysis

wordpress.org/plugins/persistent-filters

Preserves admin list filters for Posts, Pages, and WooCommerce Products. Filters like search terms, ordering and statuses are remembered per user.

0 active installs v1.3.0 PHP 7.4+ WP 4.6+ Updated Feb 28, 2026
adminfilterspersistencepostswoocommerce
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Persistent Filters Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs Updated 1mo ago
Risk Assessment

The 'persistent-filters' plugin v1.3.0 exhibits a strong security posture based on the provided static analysis. There are no identified vulnerabilities in its history and the code analysis reveals no dangerous functions, file operations, or external HTTP requests. The plugin also demonstrates good practices with all SQL queries using prepared statements and a high percentage of properly escaped output. The presence of nonce and capability checks further enhances its security.

However, the absence of any identified taint flows, while seemingly positive, could also indicate a lack of complex data handling or that the analysis might have limitations in uncovering all potential vulnerabilities. Furthermore, the total lack of any identified entry points (AJAX handlers, REST API routes, shortcodes, cron events) is unusual for a plugin and might suggest a limited functional scope or a scenario where the analysis couldn't detect them. Despite these minor observations, the overall security picture for this version of the plugin is very positive, with no immediate or critical risks identified.

Vulnerabilities
None known

Persistent Filters Security Vulnerabilities

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

Persistent Filters Release Timeline

v1.3.0Current
v1.2.0
v1.1.0
v1.0.1
v1.0.0
Code Analysis
Analyzed Mar 17, 2026

Persistent Filters Code Analysis

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

SQL Query Safety

100% prepared3 total queries

Output Escaping

89% escaped9 total outputs
Attack Surface

Persistent Filters Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 10
actionload-edit.phpincludes\persistent_filters.php:32
actionload-woocommerce_page_wc-ordersincludes\persistent_filters.php:33
actionrestrict_manage_postsincludes\persistent_filters.php:35
actionwoocommerce_order_list_table_restrict_manage_ordersincludes\persistent_filters.php:36
actionadmin_footerincludes\persistent_filters_clean.php:19
actionadmin_enqueue_scriptsincludes\persistent_filters_clean.php:20
actionadmin_post_persistent-filters_do_actionincludes\persistent_filters_clean.php:21
actionadmin_noticesincludes\persistent_filters_clean.php:22
actioninitpersistent-filters.php:87
actionplugins_loadedpersistent-filters.php:88
Maintenance & Trust

Persistent Filters Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.4
Last updatedFeb 28, 2026
PHP min version7.4
Downloads356

Community Trust

Rating100/100
Number of ratings1
Active installs0
Developer Profile

Persistent Filters Developer Profile

oveas

1 plugin · 0 total installs

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

How We Detect Persistent Filters

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/persistent-filters/css/style.css/wp-content/plugins/persistent-filters/js/scripts.js
Script Paths
/wp-content/plugins/persistent-filters/js/scripts.js
Version Parameters
persistent-filters/css/style.css?ver=persistent-filters/js/scripts.js?ver=

HTML / DOM Fingerprints

CSS Classes
pf-reset-filters-wrap
Data Attributes
data-pf-post-type
FAQ

Frequently Asked Questions about Persistent Filters