Spam_BLIP Security & Risk Analysis

wordpress.org/plugins/spam-blip

Spam BLIP stops comment spam before it is posted, using DNS blacklists, existing comments marked as spam, and user defined lists.

10 active installs v1.0.8.1 PHP + WP 4.2+ Updated Sep 25, 2020
anti-spamblog-spamcomment-spamspamspam-comments
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Spam_BLIP Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 5yr ago
Risk Assessment

The "spam-blip" v0.0.1 plugin exhibits a mixed security posture. On the positive side, it has no known historical vulnerabilities (CVEs) and a seemingly limited attack surface, with no AJAX handlers, REST API routes, or shortcodes exposed without authentication. It also avoids file operations and external HTTP requests. However, significant concerns arise from the static analysis. A substantial 47% of SQL queries are not using prepared statements, which is a direct path to SQL injection vulnerabilities. Furthermore, a critical finding is that 0% of output is properly escaped, meaning any dynamic data outputted by the plugin is highly susceptible to Cross-Site Scripting (XSS) attacks. The taint analysis also indicates two flows with unsanitized paths, which, combined with the lack of output escaping, strongly suggests potential XSS vulnerabilities.

Key Concerns

  • SQL queries not using prepared statements
  • No output escaping
  • Taint flows with unsanitized paths
Vulnerabilities
None known

Spam_BLIP Security Vulnerabilities

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

Spam_BLIP Code Analysis

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

SQL Query Safety

53% prepared15 total queries

Output Escaping

0% escaped65 total outputs
Data Flows
2 unsanitized

Data Flow Analysis

2 flows2 with unsanitized paths
do_db_bl_check (Spam_BLIP.php:2942)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Spam_BLIP Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 10
actionadmin_menuOptions_0_0_2b.inc.php:102
actionadmin_initOptions_0_0_2b.inc.php:104
actioninitSpam_BLIP.php:341
actionwidgets_initSpam_BLIP.php:346
actionwidgets_initSpam_BLIP.php:864
filtertables_to_repairSpam_BLIP.php:983
actionpre_comment_on_postSpam_BLIP.php:988
actionlogin_form_registerSpam_BLIP.php:993
actionshutdownSpam_BLIP.php:1000
actionspamblipplugincronactSpam_BLIP.php:1012

Scheduled Events 2

spamblipplugincronact
spamblipplugincronact
Maintenance & Trust

Spam_BLIP Maintenance & Trust

Maintenance Signals

WordPress version tested5.5.18
Last updatedSep 25, 2020
PHP min version
Downloads3K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Spam_BLIP Developer Profile

EdHynan

2 plugins · 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 Spam_BLIP

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/spam-blip/spamblip.css/wp-content/plugins/spam-blip/spamblip.js
Script Paths
/wp-content/plugins/spam-blip/spamblip.js
Version Parameters
spam-blip/spamblip.css?ver=spam-blip/spamblip.js?ver=

HTML / DOM Fingerprints

HTML Comments
<!-- Spam BLIP: Comment form processed. -->
JS Globals
Spam_BLIP_php52_htmlent
FAQ

Frequently Asked Questions about Spam_BLIP