Sz Comment Filter Security & Risk Analysis

wordpress.org/plugins/sz-comment-filter

No spam in comments. blocked by Invisible internal token-code with ajax.This is not used CAPTCHA.

10 active installs v1.1.2 PHP + WP 3.0+ Updated Mar 26, 2015
commentcomment-spamcommentsspamspammer
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Sz Comment Filter Safe to Use in 2026?

Generally Safe

Score 85/100

Sz Comment 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 "sz-comment-filter" plugin version 1.1.2 exhibits significant security concerns, primarily stemming from its unprotected AJAX endpoints and the presence of dangerous functions. The analysis reveals two AJAX handlers, both lacking authentication checks, which presents a substantial attack surface. Furthermore, the `unserialize` function is used twice, indicating a potential for deserialization vulnerabilities if user-controlled data is passed to it without proper sanitization. While the plugin demonstrates good practices in using prepared statements for SQL queries and has no recorded vulnerability history, these strengths are overshadowed by the critical weaknesses in input validation and authentication.

The absence of any taint analysis findings and zero known CVEs are positive indicators, suggesting that in the past, the plugin may not have been a target or has been developed with some level of security awareness. However, the static analysis clearly points to areas where vulnerabilities could easily be introduced or exploited. The low percentage of properly escaped output also raises concerns about Cross-Site Scripting (XSS) vulnerabilities, although no direct taint flows were identified for this.

In conclusion, while the plugin has a clean vulnerability history and uses prepared statements, the lack of authentication on AJAX endpoints and the use of `unserialize` create a high-risk profile. These issues could lead to arbitrary code execution, unauthorized actions, or data manipulation. Recommendations for immediate action would include implementing robust authentication and authorization checks on all AJAX handlers and carefully sanitizing any data passed to the `unserialize` function.

Key Concerns

  • AJAX handlers without authentication checks
  • Use of unserialize function
  • Low percentage of properly escaped output
  • No nonce checks on AJAX handlers
  • No capability checks on entry points
Vulnerabilities
None known

Sz Comment Filter Security Vulnerabilities

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

Sz Comment Filter Release Timeline

v1.1.2Current
v1.1.1
v1.1.0
v1.0.0
Code Analysis
Analyzed Apr 16, 2026

Sz Comment Filter Code Analysis

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

Dangerous Functions Found

unserialize$ret_array[$idx]=unserialize($szmcf_data[$keyname]);szmcf-functions.php:134
unserialize$ret_array[$idx]=unserialize($szmcf_data[$keyname]);szmcf-functions.php:148

Output Escaping

30% escaped23 total outputs
Attack Surface
2 unprotected

Sz Comment Filter Attack Surface

Entry Points2
Unprotected2

AJAX Handlers 2

authwp_ajax_szmcf_currentkeysz-comment-filter.php:128
noprivwp_ajax_szmcf_currentkeysz-comment-filter.php:129
WordPress Hooks 11
actioninitsz-comment-filter.php:35
actionwp_enqueue_scriptssz-comment-filter.php:66
actioncomment_form_after_fieldssz-comment-filter.php:106
actioncomment_form_logged_in_aftersz-comment-filter.php:107
actionwp_headsz-comment-filter.php:120
filterpreprocess_commentsz-comment-filter.php:213
actionadmin_enqueue_scriptsszmcf-admin.php:25
actionadmin_noticesszmcf-admin.php:107
filterscreen_layout_columnsszmcf-admin.php:143
actionadmin_headszmcf-admin.php:145
actionadmin_initszmcf-admin.php:165
Maintenance & Trust

Sz Comment Filter Maintenance & Trust

Maintenance Signals

WordPress version tested4.1.42
Last updatedMar 26, 2015
PHP min version
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Sz Comment Filter Developer Profile

SzMake

1 plugin · 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 Sz Comment Filter

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/sz-comment-filter/css/styles-admin.css/wp-content/plugins/sz-comment-filter/js/scripts-admin.js/wp-content/plugins/sz-comment-filter/js/sz-comment-filter.js
Script Paths
/wp-content/plugins/sz-comment-filter/js/sz-comment-filter.js/wp-content/plugins/sz-comment-filter/js/scripts-admin.js
Version Parameters
sz-comment-filter/js/sz-comment-filter.js?ver=sz-comment-filter/js/scripts-admin.js?ver=sz-comment-filter/css/styles-admin.css?ver=

HTML / DOM Fingerprints

CSS Classes
szmcf-inputszmcf-hunnypot
Data Attributes
name="szmcf-email-website-url"id="szmcf-email-website-url"class="szmcf-param"name="szmcf-key"id="szmcf-key"class="szmcf-param"+4 more
JS Globals
var szmcf_ajaxurl
REST Endpoints
/wp-json/szmcf_currentkey
FAQ

Frequently Asked Questions about Sz Comment Filter