WP Email Invisibliser Security & Risk Analysis

wordpress.org/plugins/wp-email-invisibliser

A simple plugin to hide emails from spambots. Simply use the shortcode [hide_email myemail@mydomain.com] to hide myemail@mydomain.

100 active installs v0.1.2 PHP + WP 2.0.2+ Updated Nov 18, 2012
antispamemailmanglemungeobscure
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is WP Email Invisibliser Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 13yr ago
Risk Assessment

The 'wp-email-invisibliser' v0.1.2 plugin exhibits a generally positive security posture based on the provided static analysis and vulnerability history. The code successfully employs prepared statements for all SQL queries, demonstrates proper output escaping for all outputs, and has no recorded file operations or external HTTP requests. Crucially, there are no identified critical or high-severity taint flows, indicating a lack of easily exploitable data manipulation vulnerabilities within the analyzed code.

However, there are several areas that warrant attention. The absence of any nonce checks and capability checks is a significant concern. While the current attack surface is small and appears to have no unprotected entry points in this specific analysis, these checks are fundamental security mechanisms that prevent a wide range of attacks, including Cross-Site Request Forgery (CSRF) and unauthorized access. The presence of a shortcode as an entry point without any associated authentication or permission checks, even if it's the only entry point, represents a potential vulnerability if the shortcode's functionality is sensitive or can be manipulated.

The vulnerability history being completely clear is a positive sign, suggesting the developers have a good track record or that the plugin has not been subjected to extensive security scrutiny. Nevertheless, the lack of protective measures like nonce and capability checks means that even a simple, seemingly harmless shortcode could become a vector for attacks if its functionality is not robustly secured.

Key Concerns

  • Missing Nonce Checks
  • Missing Capability Checks
  • Shortcode without Auth Checks
Vulnerabilities
None known

WP Email Invisibliser Security Vulnerabilities

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

WP Email Invisibliser Code Analysis

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

WP Email Invisibliser Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[hide_email] wp_email_invisibliser.php:27
WordPress Hooks 1
filterthe_postswp_email_invisibliser.php:42
Maintenance & Trust

WP Email Invisibliser Maintenance & Trust

Maintenance Signals

WordPress version tested3.4.2
Last updatedNov 18, 2012
PHP min version
Downloads4K

Community Trust

Rating100/100
Number of ratings5
Active installs100
Developer Profile

WP Email Invisibliser Developer Profile

Adam Sargant

4 plugins · 130 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 Email Invisibliser

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/wp-email-invisibliser/js/hide_email.js
Script Paths
/wp-content/plugins/wp-email-invisibliser/js/hide_email.js
Version Parameters
wp-email-invisibliser/js/hide_email.js?ver=

HTML / DOM Fingerprints

CSS Classes
wp_hide_email
Shortcode Output
<span class='wp_hide_email
FAQ

Frequently Asked Questions about WP Email Invisibliser