Geek Mail Blacklist Security & Risk Analysis

wordpress.org/plugins/geek-mail-blacklist

Block users with certain emails from registering to your WordPress site by adding blacklist rules.

0 active installs v1.1.0 PHP + WP 3.9+ Updated Unknown
blacklistemailspam
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Geek Mail Blacklist Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs
Risk Assessment

The "geek-mail-blacklist" v1.1.0 plugin exhibits a generally strong security posture based on the provided static analysis. A significant strength is the complete absence of direct SQL injection vulnerabilities, with all queries utilizing prepared statements. Furthermore, the plugin demonstrates good practices in output escaping, with 90% of outputs properly handled, and the taint analysis reveals no critical or high-severity unsanitized flows. The lack of file operations, external HTTP requests, and shortcodes/cron events also reduces the potential attack surface. The vulnerability history being completely clear is a very positive indicator, suggesting a history of secure development or prompt patching.

However, there are areas for improvement. The plugin has 6 AJAX handlers, and while the static analysis indicates 0 are unprotected, the absence of explicit capability checks on these AJAX handlers is a notable concern. Relying solely on nonce checks for AJAX security, especially without explicit capability checks, can leave the plugin vulnerable to authorization bypass if nonces are compromised or if actions are intended to be restricted to specific user roles. The plugin also has no recorded vulnerability history, which is positive, but the lack of capability checks in the code is a weakness that could lead to future issues if not addressed.

Key Concerns

  • AJAX handlers without capability checks
Vulnerabilities
None known

Geek Mail Blacklist Security Vulnerabilities

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

Geek Mail Blacklist Code Analysis

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

SQL Query Safety

100% prepared17 total queries

Output Escaping

90% escaped58 total outputs
Data Flows
All sanitized

Data Flow Analysis

7 flows
ajaxGetRulePage (backend\actions.php:23)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Geek Mail Blacklist Attack Surface

Entry Points6
Unprotected0

AJAX Handlers 6

authwp_ajax_gmb_enablebackend\actions.php:6
authwp_ajax_gmb_delbackend\actions.php:7
authwp_ajax_gmb_get_rules_pagebackend\actions.php:8
authwp_ajax_gmb_del_recordsbackend\monitor.php:12
authwp_ajax_gmb_get_monitor_counts_pagebackend\monitor.php:13
authwp_ajax_gmb_get_monitor_records_pagebackend\monitor.php:14
Maintenance & Trust

Geek Mail Blacklist Maintenance & Trust

Maintenance Signals

WordPress version tested5.1.22
Last updatedUnknown
PHP min version
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

Geek Mail Blacklist Developer Profile

gongwan33

3 plugins · 10 total installs

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

How We Detect Geek Mail Blacklist

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/geek-mail-blacklist/css/style.css
Version Parameters
geek-mail-blacklist/css/style.css?ver=

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Geek Mail Blacklist