Block Disposable Email Security & Risk Analysis

wordpress.org/plugins/block-disposable-email-addresses

This plugin detects one-time email addresses (disposable email, trashmail, mailinator, 10minutemail) and helps to keep your userbase and comments clea …

10 active installs v0.8 PHP + WP 3.3.1+ Updated Mar 16, 2017
commentsdisposable-emailpostsspamtemporary-email
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Block Disposable Email Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 9yr ago
Risk Assessment

The 'block-disposable-email-addresses' plugin version 0.8 exhibits a mixed security posture. On the positive side, it demonstrates good practices by having a remarkably small attack surface with zero identified entry points (AJAX, REST API, shortcodes, cron events) and also utilizes prepared statements for all its SQL queries. The absence of known CVEs and a clean vulnerability history further suggests a generally well-maintained codebase in terms of disclosed vulnerabilities.

However, significant concerns arise from the static analysis. The most critical finding is that 100% of its five identified output points are not properly escaped. This represents a high risk for Cross-Site Scripting (XSS) vulnerabilities, where malicious code could be injected and executed in the user's browser. Additionally, while the taint analysis found no critical or high severity unsanitized paths, the presence of two flows with unsanitized paths, even if deemed of lower severity by the analysis, warrants attention. The lack of nonce and capability checks on its (albeit zero) entry points is a missed opportunity for defense-in-depth, though less critical given the absence of actual entry points.

In conclusion, while the plugin's small attack surface and SQL practices are commendable, the complete lack of output escaping is a major security flaw that exposes users to XSS attacks. The vulnerability history is clean, but this should not lull developers into a false sense of security, as the code analysis itself reveals significant potential weaknesses. Addressing the output escaping issue should be the absolute top priority.

Key Concerns

  • 0% of output properly escaped
  • 2 flows with unsanitized paths
  • 0 nonce checks
  • 0 capability checks
Vulnerabilities
None known

Block Disposable Email Security Vulnerabilities

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

Block Disposable Email Code Analysis

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

Output Escaping

0% escaped5 total outputs
Data Flows
2 unsanitized

Data Flow Analysis

2 flows2 with unsanitized paths
plugin_section_text (bdea.php:31)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Block Disposable Email Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 7
actionadmin_menubdea.php:23
actionadmin_initbdea.php:28
filterplugin_action_linksbdea.php:99
filteris_emailbdea.php:141
filterpreprocess_commentbdea.php:146
filterregistration_errorsbdea.php:150
actionadmin_noticesbdea.php:237
Maintenance & Trust

Block Disposable Email Maintenance & Trust

Maintenance Signals

WordPress version tested4.6.30
Last updatedMar 16, 2017
PHP min version
Downloads4K

Community Trust

Rating46/100
Number of ratings3
Active installs10
Developer Profile

Block Disposable Email Developer Profile

gsetz

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 Block Disposable Email

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

Asset Fingerprints

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Block Disposable Email