eHive Access Security & Risk Analysis

wordpress.org/plugins/ehive-access

The base plugin for the eHive plugin suite.

70 active installs v2.4.2 PHP 5.3+ WP 3.3.1+ Updated Sep 24, 2025
archivecollectionehivehistorymuseum
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is eHive Access Safe to Use in 2026?

Generally Safe

Score 100/100

eHive Access has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 7mo ago
Risk Assessment

The ehive-access plugin v2.4.2 demonstrates a relatively strong security posture based on the static analysis provided, particularly in its lack of identified dangerous functions, SQL injection vulnerabilities (all queries use prepared statements), and absence of known CVEs. The plugin also shows no file operations or bundled libraries, which can sometimes introduce vulnerabilities if not managed carefully. However, significant concerns arise from the extremely low percentage of properly escaped output (only 6%) and the complete absence of nonce checks and capability checks. This means that any data outputted by the plugin is highly susceptible to cross-site scripting (XSS) attacks, and there are no built-in protections to ensure only authorized users can interact with its functionalities, if any were exposed through the current attack surface.

Key Concerns

  • Low output escaping (6%)
  • No nonce checks
  • No capability checks
Vulnerabilities
None known

eHive Access Security Vulnerabilities

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

eHive Access Release Timeline

v2.4.2Current
v2.4.1
v2.4.0
v2.3.5
v2.3.4
v2.3.3
v2.3.2
v2.3.1
v2.3.0
v2.2.4
v2.2.3
v2.2.2
v2.2.1
v2.2.0
v2.1.4
v2.1.3
v2.1.2
v2.1.1
Code Analysis
Analyzed Mar 16, 2026

eHive Access Code Analysis

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

Output Escaping

6% escaped16 total outputs
Attack Surface

eHive Access Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 4
actionadmin_initEHiveAccess.php:38
actionadmin_menuEHiveAccess.php:40
actionactivate_ehive-access/EHiveAccess.phpEHiveAccess.php:591
actiondeactivate_ehive-access/EHiveAccess.phpEHiveAccess.php:592
Maintenance & Trust

eHive Access Maintenance & Trust

Maintenance Signals

WordPress version tested6.8.5
Last updatedSep 24, 2025
PHP min version5.3
Downloads4K

Community Trust

Rating100/100
Number of ratings1
Active installs70
Developer Profile

eHive Access Developer Profile

Vernon Systems Limited

11 plugins · 360 total installs

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

How We Detect eHive Access

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/ehive-access/css/eHiveAdmin.css/wp-content/plugins/ehive-access/js/options.js
Script Paths
options.js
Version Parameters
ehive-access/css/eHiveAdmin.css?ver=ehive-access/js/options.js?ver=

HTML / DOM Fingerprints

CSS Classes
eHiveAdminCSS
HTML Comments
eHive Access Admin OptionsCopyright (C) 2012 Vernon Systems LimitedThis program is free software; you can redistribute it and/ormodify it under the terms of the GNU General Public License+58 more
Data Attributes
id="ehive_access_options"name="ehive_access_options"value="
JS Globals
jQuery$
FAQ

Frequently Asked Questions about eHive Access