WP Emails Encoder Security & Risk Analysis

wordpress.org/plugins/fay-emails-encoder

Encode emails to avoid spams. Template to use [@encode@ email="ilove@gmail.com" display="Gmail Lover"]

60 active installs v3.1.1 PHP + WP 3.0+ Updated May 24, 2016
emailencodesecurityspam
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is WP Emails Encoder Safe to Use in 2026?

Generally Safe

Score 85/100

WP Emails Encoder 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 "fay-emails-encoder" plugin v3.1.1 exhibits a generally strong security posture based on the provided static analysis. The plugin has no known CVEs, zero recorded vulnerabilities, and a small attack surface with no apparent unprotected entry points like AJAX handlers, REST API routes, or shortcodes. The code also demonstrates good practices by not performing file operations or external HTTP requests, and all SQL queries are secured with prepared statements.

However, there are significant concerns regarding output escaping and taint analysis. A concerning 100% of the identified output points are not properly escaped, which could lead to cross-site scripting (XSS) vulnerabilities if the data originates from untrusted sources. Furthermore, the taint analysis reveals one flow with an unsanitized path, which, while not classified as critical or high severity, warrants attention as it indicates a potential pathway for malicious data to be processed without proper validation.

The lack of any vulnerability history is a positive indicator, suggesting the developers have a history of producing secure code or have effectively addressed past issues. However, the presence of unescaped output and unsanitized taint flows in this version are notable weaknesses that should be addressed to maintain this strong record.

Key Concerns

  • Outputs not properly escaped
  • Flows with unsanitized paths
Vulnerabilities
None known

WP Emails Encoder Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Version History

WP Emails Encoder Release Timeline

v2.5
v1.0
Code Analysis
Analyzed Mar 16, 2026

WP Emails Encoder Code Analysis

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

Output Escaping

0% escaped2 total outputs
Data Flows · Security
1 unsanitized

Data Flow Analysis

2 flows1 with unsanitized paths
options_page (fay-emails-encoder.php:59)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

WP Emails Encoder Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 4
actionadmin_menufay-emails-encoder.php:17
actionadmin_initfay-emails-encoder.php:18
filtermedia_buttons_contextfay-emails-encoder.php:19
filterthe_contentfay-emails-encoder.php:22
Maintenance & Trust

WP Emails Encoder Maintenance & Trust

Maintenance Signals

WordPress version tested4.5.33
Last updatedMay 24, 2016
PHP min version
Downloads6K

Community Trust

Rating100/100
Number of ratings1
Active installs60
Developer Profile

WP Emails Encoder Developer Profile

.fay

6 plugins · 390 total installs

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

How We Detect WP Emails Encoder

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/fay-emails-encoder/email-encoder.js
Script Paths
/wp-content/plugins/fay-emails-encoder/email-encoder.js

HTML / DOM Fingerprints

HTML Comments
<!-- Last Action -->
Data Attributes
id="email-encoder"name="fee_active"value="yes"name="fee_submit"
Shortcode Output
<a href="mailto:">
FAQ

Frequently Asked Questions about WP Emails Encoder