Block Spammers Security & Risk Analysis

wordpress.org/plugins/block-spammers

Block spammers from submitting comments, by IPs or by bad words.

40 active installs v0.3 PHP + WP 3.5.1+ Updated Oct 25, 2018
blockingcommentsipspam
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Block Spammers Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 7yr ago
Risk Assessment

The 'block-spammers' plugin v0.3 exhibits a generally good security posture based on the provided static analysis and vulnerability history. The lack of identified vulnerabilities, critical taint flows, and a clean vulnerability history suggest that the developers have followed secure coding practices. Furthermore, the absence of dangerous functions, file operations, and external HTTP requests is a positive sign. The limited attack surface, with no identified AJAX handlers, REST API routes, shortcodes, or cron events that are exposed without authentication or proper checks, further strengthens its security. The plugin also demonstrates good practices in output escaping, with a high percentage of outputs being properly sanitized. However, a significant concern arises from the use of raw SQL queries without prepared statements. While there are only two such queries, this practice leaves the plugin vulnerable to SQL injection attacks, especially if the data used in these queries originates from user input. The lack of nonce checks and capability checks also indicates a potential area for improvement in securing any future functionalities that might be added.

Key Concerns

  • SQL queries not using prepared statements
  • Missing nonce checks
  • Missing capability checks
Vulnerabilities
None known

Block Spammers Security Vulnerabilities

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

Block Spammers Code Analysis

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

SQL Query Safety

0% prepared2 total queries

Output Escaping

75% escaped8 total outputs
Attack Surface

Block Spammers Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 6
actionadmin_menublock-spammers-admin.php:19
actionadmin_initblock-spammers-admin.php:20
actiondelete_commentblock-spammers-admin.php:21
actionadmin_enqueue_scriptsblock-spammers-admin.php:22
filterpreprocess_commentblock-spammers.php:25
actioninitblock-spammers.php:26
Maintenance & Trust

Block Spammers Maintenance & Trust

Maintenance Signals

WordPress version tested5.0.25
Last updatedOct 25, 2018
PHP min version
Downloads3K

Community Trust

Rating0/100
Number of ratings0
Active installs40
Developer Profile

Block Spammers Developer Profile

sander85

1 plugin · 40 total installs

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

How We Detect Block Spammers

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/block-spammers/js/main.js
Script Paths
/wp-content/plugins/block-spammers/js/main.js

HTML / DOM Fingerprints

HTML Comments
Block Spammers by Sander Lepik To the extent possible under law, the person who associated CC0 with Block Spammers has waived all copyright and related or neighboring rights to Block Spammers. You should have received a copy of the CC0 legalcode along with this work. If not, see <http://creativecommons.org/publicdomain/zero/1.0/>.No script kiddies please!
FAQ

Frequently Asked Questions about Block Spammers