GSY Content Filter Security & Risk Analysis

wordpress.org/plugins/gsy-content-filter

Filter words from the title, content, excerpt or tags in posts.

10 active installs v1.0 PHP + WP 3.0.1+ Updated Jan 18, 2015
filterpermanenttemporarilytitlewords
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is GSY Content Filter Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 11yr ago
Risk Assessment

The static analysis of the gsy-content-filter v1.0 plugin reveals a generally positive security posture, with no identified attack vectors through AJAX handlers, REST API routes, shortcodes, or cron events. The absence of dangerous functions, file operations, and external HTTP requests further contributes to a reduced risk profile. Notably, all SQL queries are correctly handled using prepared statements, and there are no recorded vulnerabilities, indicating a proactive approach to security by the developers or a lack of prior exposure. However, a weakness is present in output escaping, with only 63% of outputs being properly escaped. This suggests a potential for cross-site scripting (XSS) vulnerabilities if user-supplied data is not sufficiently sanitized before being rendered on the front end. While the plugin has no vulnerability history, this could also mean it hasn't been extensively tested or targeted. The lack of nonce and capability checks, while not directly posing an immediate risk given the zero attack surface, represents a missed opportunity for robust authorization and security hardening if any entry points were to be introduced in the future.

Key Concerns

  • Unescaped output
  • No nonce checks
  • No capability checks
Vulnerabilities
None known

GSY Content Filter Security Vulnerabilities

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

GSY Content Filter Code Analysis

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

Output Escaping

63% escaped8 total outputs
Attack Surface

GSY Content Filter Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 8
actionadmin_enqueue_scriptsincludes\class-gsy-content-filter.php:30
actionadmin_enqueue_scriptsincludes\class-gsy-content-filter.php:31
actionadmin_menuincludes\class-gsy-content-filter.php:32
actionadmin_initincludes\class-gsy-content-filter.php:33
filterthe_titleincludes\class-gsy-content-filter.php:283
filterthe_contentincludes\class-gsy-content-filter.php:284
filterthe_excerptincludes\class-gsy-content-filter.php:285
filterthe_tagsincludes\class-gsy-content-filter.php:286
Maintenance & Trust

GSY Content Filter Maintenance & Trust

Maintenance Signals

WordPress version tested4.1.42
Last updatedJan 18, 2015
PHP min version
Downloads2K

Community Trust

Rating100/100
Number of ratings2
Active installs10
Developer Profile

GSY Content Filter Developer Profile

GSY

3 plugins · 30 total installs

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

How We Detect GSY Content Filter

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/gsy-content-filter/css/style.css/wp-content/plugins/gsy-content-filter/js/script.js
Script Paths
/wp-content/plugins/gsy-content-filter/js/script.js
Version Parameters
gsy-content-filter/css/style.css?ver=gsy-content-filter/js/script.js?ver=

HTML / DOM Fingerprints

CSS Classes
gsy-content-filter
FAQ

Frequently Asked Questions about GSY Content Filter