Entity Viewer Security & Risk Analysis

wordpress.org/plugins/entity-viewer

Displays properties and custom fields of WordPress entities (posts, users, terms, comments) for debugging/development purposes.

100 active installs v0.5.2 PHP 7.4+ WP 5.7+ Updated Sep 13, 2024
customdisplayfieldmetametabox
92
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Entity Viewer Safe to Use in 2026?

Generally Safe

Score 92/100

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

No known CVEs Updated 1yr ago
Risk Assessment

The entity-viewer plugin v0.5.2 exhibits a mixed security posture. On the positive side, it demonstrates good practices by utilizing prepared statements for all SQL queries and has no recorded vulnerability history, suggesting a generally stable codebase. However, significant concerns arise from the static analysis. The plugin exposes a single AJAX handler without any authentication or authorization checks, creating a direct attack vector. Furthermore, the presence of the `unserialize` function, especially in conjunction with an unprotected entry point, is a critical red flag as it can lead to arbitrary code execution if user-supplied data is unserialized without proper validation. While taint analysis found no issues, this might be due to the limited scope or the nature of the input, and the `unserialize` vulnerability remains a potent threat. The lack of capability checks on the AJAX endpoint is also a notable weakness.

Key Concerns

  • AJAX handler without auth check
  • Dangerous function: unserialize
  • Nonce check missing on AJAX
  • Capability check missing
Vulnerabilities
None known

Entity Viewer Security Vulnerabilities

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

Entity Viewer Release Timeline

v0.5.2Current
v0.5.1
v0.5.0
Code Analysis
Analyzed Mar 16, 2026

Entity Viewer Code Analysis

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

Dangerous Functions Found

unserialize$value_pretty = $is_value_serialized ? var_export(unserialize($item['meta_value']), true) : '';src\inc\logic.php:268

SQL Query Safety

100% prepared4 total queries

Output Escaping

67% escaped12 total outputs
Attack Surface
1 unprotected

Entity Viewer Attack Surface

Entry Points1
Unprotected1

AJAX Handlers 1

authwp_ajax_vsm_refresh_datasrc\Plugin.php:32
WordPress Hooks 11
actionadmin_noticesentity-viewer.php:37
actionadmin_noticesentity-viewer.php:44
actioninitentity-viewer.php:57
actionadmin_footersrc\inc\logic.php:177
filteroverride_load_textdomainsrc\Plugin.php:27
actionadd_meta_boxessrc\Plugin.php:38
actionedit_user_profilesrc\Plugin.php:41
actionshow_user_profilesrc\Plugin.php:42
actionadmin_print_scriptssrc\Plugin.php:45
actionadd_meta_boxes_commentsrc\Plugin.php:48
actionadmin_enqueue_scriptssrc\Plugin.php:51
Maintenance & Trust

Entity Viewer Maintenance & Trust

Maintenance Signals

WordPress version tested6.6.5
Last updatedSep 13, 2024
PHP min version7.4
Downloads2K

Community Trust

Rating100/100
Number of ratings2
Active installs100
Developer Profile

Entity Viewer Developer Profile

versusbassz

2 plugins · 400 total installs

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

How We Detect Entity Viewer

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/entity-viewer/assets/css/main.css/wp-content/plugins/entity-viewer/assets/js/main.js
Script Paths
/wp-content/plugins/entity-viewer/assets/js/main.js
Version Parameters
entity-viewer/assets/css/main.css?ver=entity-viewer/assets/js/main.js?ver=

HTML / DOM Fingerprints

CSS Classes
ev-entity-viewer-tab
HTML Comments
<!-- ev-track-field -->
Data Attributes
data-ev-track-field
JS Globals
window.entityViewer
FAQ

Frequently Asked Questions about Entity Viewer