wL Email Encrypter Security & Risk Analysis

wordpress.org/plugins/wl-email-encrypter

This plugin encrypted e-mail addresses to protect and hide them from bots and harvesters.

90 active installs v1.0.5 PHP + WP 2.9+ Updated Mar 28, 2011
emailencrypthideprotectspam
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is wL Email Encrypter Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 15yr ago
Risk Assessment

The wl-email-encrypter plugin v1.0.5 exhibits a mixed security posture, with some positive indicators but notable concerns regarding output escaping and the use of a dangerous function. While the plugin has no recorded vulnerability history, this could be due to limited discovery rather than inherent security. The static analysis reveals a small attack surface with no unprotected entry points, and SQL queries are securely handled with prepared statements. Nonce checks are present. However, a significant weakness is the complete lack of output escaping, meaning any dynamic data displayed could be vulnerable to cross-site scripting (XSS) attacks. Furthermore, the presence of the `unserialize` function is a red flag, as it can be a vector for remote code execution (RCE) if an attacker can control the data being unserialized.

Key Concerns

  • All output is unescaped
  • Uses dangerous function unserialize
  • Missing capability checks
Vulnerabilities
None known

wL Email Encrypter Security Vulnerabilities

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

wL Email Encrypter Code Analysis

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

Dangerous Functions Found

unserialize$this->options = unserialize($this->options);includes\wlee_class.php:580

Output Escaping

0% escaped34 total outputs
Data Flows
All sanitized

Data Flow Analysis

2 flows
options_page (includes\wlee_class.php:648)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

wL Email Encrypter Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[wlee_options] includes\wlee_class.php:29
WordPress Hooks 14
actionadmin_menuincludes\wlee_class.php:13
filterplugin_row_metaincludes\wlee_class.php:25
actioninitincludes\wlee_class.php:34
actionwpincludes\wlee_class.php:39
actionadmin_menuincludes\wlee_class.php:41
actionwp_insert_postincludes\wlee_class.php:42
actionwp_update_postincludes\wlee_class.php:43
filterthe_contentincludes\wlee_class.php:63
filterthe_excerptincludes\wlee_class.php:64
filtercomment_textincludes\wlee_class.php:69
filterwidget_textincludes\wlee_class.php:76
filterwidget_contentincludes\wlee_class.php:80
filterthe_content_feedincludes\wlee_class.php:86
filterthe_excerpt_rssincludes\wlee_class.php:87
Maintenance & Trust

wL Email Encrypter Maintenance & Trust

Maintenance Signals

WordPress version tested4.6.30
Last updatedMar 28, 2011
PHP min version
Downloads11K

Community Trust

Rating0/100
Number of ratings0
Active installs90
Developer Profile

wL Email Encrypter Developer Profile

brewlabs

5 plugins · 2K total installs

60
trust score
Avg Security Score
73/100
Avg Patch Time
1682 days
View full developer profile
Detection Fingerprints

How We Detect wL Email Encrypter

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/wl-email-encrypter/js/wlee.js
Script Paths
/wp-content/plugins/wl-email-encrypter/js/wlee.js
Version Parameters
wl-email-encrypter/js/wlee.js?ver=

HTML / DOM Fingerprints

Shortcode Output
<input type="radio" name="wlee_post_encrypt_method" value="default"
FAQ

Frequently Asked Questions about wL Email Encrypter