Exclude Search Security & Risk Analysis

wordpress.org/plugins/exclude-search

Exclude posts, pages, products or custom posts from WordPress search results.

80 active installs v1.0.2 PHP 7.4+ WP 6.1.7+ Updated Jan 31, 2025
exclude-from-searchexclude-pageexclude-posthide-from-searchsearch-exclude
92
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Exclude Search Safe to Use in 2026?

Generally Safe

Score 92/100

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

No known CVEs Updated 1yr ago
Risk Assessment

The "exclude-search" v1.0.2 plugin exhibits a strong security posture based on the provided static analysis. The plugin demonstrates excellent adherence to secure coding practices, with no identified dangerous functions, all SQL queries utilizing prepared statements, and all output properly escaped. The absence of file operations and external HTTP requests further reduces its attack surface. Furthermore, the presence of nonce and capability checks indicates an effort to protect against common WordPress vulnerabilities.

The static analysis found no critical or high severity taint flows, and the vulnerability history is clean, with zero known CVEs. This indicates a low risk of known exploits. The total attack surface is also zero, meaning there are no direct entry points like AJAX handlers, REST API routes, or shortcodes that could be directly targeted by attackers. This lack of entry points, combined with robust internal checks, suggests a well-hardened plugin.

Overall, this plugin appears to be very secure. Its strengths lie in its clean code, minimal attack surface, and proactive use of security features like prepared statements, output escaping, nonces, and capability checks. The absence of any vulnerability history further reinforces its positive security profile. There are no specific risks flagged by the code analysis or vulnerability history that would warrant significant concern at this time.

Vulnerabilities
None known

Exclude Search Security Vulnerabilities

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

Exclude Search Code Analysis

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

Output Escaping

100% escaped35 total outputs
Data Flows
All sanitized

Data Flow Analysis

2 flows
display_tab_content (exclude-search.php:336)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Exclude Search Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 4
actionadmin_menuexclude-search.php:65
actionadmin_enqueue_scriptsexclude-search.php:66
actionadmin_initexclude-search.php:67
filterpre_get_postsexclude-search.php:68
Maintenance & Trust

Exclude Search Maintenance & Trust

Maintenance Signals

WordPress version tested6.7.5
Last updatedJan 31, 2025
PHP min version7.4
Downloads1K

Community Trust

Rating100/100
Number of ratings1
Active installs80
Developer Profile

Exclude Search Developer Profile

Jainish Brahmbhatt

1 plugin · 80 total installs

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

How We Detect Exclude Search

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/exclude-search/assets/css/admin-style.css/wp-content/plugins/exclude-search/assets/js/custom.js
Script Paths
/wp-content/plugins/exclude-search/assets/js/custom.js
Version Parameters
exclude-search/assets/css/admin-style.css?ver=exclude-search/assets/js/custom.js?ver=

HTML / DOM Fingerprints

JS Globals
excludesearchcustomAjax
FAQ

Frequently Asked Questions about Exclude Search