Local Email Blocker Security & Risk Analysis

wordpress.org/plugins/local-email-blocker

Blocks outgoing emails in development environments and logs them for review.

0 active installs v1.2.1 PHP 8.1+ WP 5.0+ Updated Unknown
blockdevelopmentemaillogstaging
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Local Email Blocker Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs
Risk Assessment

The "local-email-blocker" plugin v1.2.1 exhibits a generally good security posture with a significant number of entry points (6 AJAX handlers) protected by nonce checks. The absence of any recorded vulnerabilities in its history is a strong indicator of a well-maintained and secure plugin. However, the static analysis reveals a couple of areas that warrant attention. The presence of the `unserialize` function, especially without clear sanitization context, is a potential risk for deserialization vulnerabilities. Furthermore, the taint analysis indicates four flows with unsanitized paths, all classified as high severity, which is a notable concern that needs further investigation. While the plugin benefits from prepared statements for most SQL queries and a good proportion of properly escaped outputs, the identified taint flows and the use of `unserialize` are the primary weaknesses that detract from an otherwise solid security foundation.

Key Concerns

  • High severity unsanitized taint flows (4)
  • Dangerous function: unserialize
  • Output escaping: 44% not properly escaped
Vulnerabilities
None known

Local Email Blocker Security Vulnerabilities

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

Local Email Blocker Code Analysis

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

Dangerous Functions Found

unserialize$attachments = unserialize($email->attachments);admin\email-details.php:17
unserialize$attachments = unserialize($email->attachments);templates\admin\email-details.php:17

SQL Query Safety

67% prepared12 total queries

Output Escaping

56% escaped78 total outputs
Data Flows
4 unsanitized

Data Flow Analysis

6 flows4 with unsanitized paths
<email-log-page> (admin\email-log-page.php:0)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Local Email Blocker Attack Surface

Entry Points6
Unprotected0

AJAX Handlers 6

authwp_ajax_lebdev_get_email_detailsAdmin.php:20
authwp_ajax_lebdev_delete_emailAdmin.php:21
authwp_ajax_lebdev_clear_all_emailsAdmin.php:22
authwp_ajax_lebdev_get_email_detailssrc\Admin.php:20
authwp_ajax_lebdev_delete_emailsrc\Admin.php:21
authwp_ajax_lebdev_clear_all_emailssrc\Admin.php:22
WordPress Hooks 19
actionadmin_menuAdmin.php:18
actionadmin_initAdmin.php:19
actionadmin_enqueue_scriptsAdmin.php:23
filterset-screen-optionAdmin.php:24
actioninitEmailBlocker.php:26
filterwp_mailEmailBlocker.php:32
actionphpmailer_initEmailBlocker.php:33
actionphpmailer_initEmailBlocker.php:97
filterwp_mailEmailBlocker.php:102
actionplugins_loadedlocal-email-blocker.php:43
actionadmin_menusrc\Admin.php:18
actionadmin_initsrc\Admin.php:19
actionadmin_enqueue_scriptssrc\Admin.php:23
filterset-screen-optionsrc\Admin.php:24
actioninitsrc\EmailBlocker.php:26
filterwp_mailsrc\EmailBlocker.php:32
actionphpmailer_initsrc\EmailBlocker.php:33
actionphpmailer_initsrc\EmailBlocker.php:97
filterwp_mailsrc\EmailBlocker.php:102
Maintenance & Trust

Local Email Blocker Maintenance & Trust

Maintenance Signals

WordPress version tested6.8.5
Last updatedUnknown
PHP min version8.1
Downloads251

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

Local Email Blocker Developer Profile

Md Mostafizur Rahman

1 plugin · 0 total installs

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

How We Detect Local Email Blocker

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/local-email-blocker/assets/css/email-log.css/wp-content/plugins/local-email-blocker/assets/js/email-log.js/wp-content/plugins/local-email-blocker/assets/js/settings.js
Script Paths
/wp-content/plugins/local-email-blocker/assets/js/email-log.js/wp-content/plugins/local-email-blocker/assets/js/settings.js
Version Parameters
local-email-blocker/assets/css/email-log.css?ver=local-email-blocker/assets/js/email-log.js?ver=local-email-blocker/assets/js/settings.js?ver=

HTML / DOM Fingerprints

CSS Classes
lebdev-email-log-tablelebdev-email-details-modallebdev-settings-form
HTML Comments
<!-- Email Log Settings --><!-- Email Details Modal --><!-- Email Log Table -->
Data Attributes
data-email-iddata-actiondata-securitydata-nonce
JS Globals
lebdev_ajax_object
REST Endpoints
/wp-json/local-email-blocker/v1/get-email-details/wp-json/local-email-blocker/v1/delete-email/wp-json/local-email-blocker/v1/clear-all-emails
FAQ

Frequently Asked Questions about Local Email Blocker