Sitewise Security & Risk Analysis

wordpress.org/plugins/wp-call-me-back

Add an on-page assistant that answers only from your own content, plus the classic request-a-call-back form. Grounded, cheap, no SaaS lock-in.

30 active installs v4.0.2 PHP 7.4+ WP 6.4+ Updated Jun 13, 2026
aiassistantcall-backchatbotcustomer-support
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Sitewise Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs Updated 2mo ago
Risk Assessment

The "wp-call-me-back" v3.4.1 plugin exhibits a mixed security posture. On the positive side, the plugin has no known historical vulnerabilities (CVEs), suggesting a generally stable and well-maintained codebase. Furthermore, the static analysis reveals a seemingly small attack surface with no apparent AJAX handlers, REST API routes, shortcodes, or cron events exposed without proper authentication checks. This is a strong indicator of good practice regarding access control.

Key Concerns

  • 11 dangerous functions found (unserialize)
  • 50% SQL queries not using prepared statements
  • Only 17% of outputs properly escaped
  • 0 Nonce checks found
  • 0 Capability checks found
  • 12 flows with unsanitized paths
  • 3 High severity taint flows found
Vulnerabilities
None known

Sitewise Security Vulnerabilities

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

Sitewise Release Timeline

v4.0.2Current
v4.0.1
v4.0.0
Code Analysis
Analyzed Mar 16, 2026

Sitewise Code Analysis

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

Dangerous Functions Found

unserialize$get_option_details = unserialize(get_option('rcb_settings_options'));wp-callmeback.php:32
unserialize$get_recaptcha_details = unserialize(get_option('rcb_recaptcha_options'));wp-callmeback.php:33
unserialize$get_option_details = unserialize(get_option('rcb_settings_options'));wp-callmeback.php:649
unserialize$get_recaptcha_details = unserialize(get_option('rcb_recaptcha_options'));wp-callmeback.php:650
unserialize$get_option_details = unserialize(get_option('rcb_recaptcha_options'));wp-callmeback.php:907
unserialize$get_option_details = unserialize(get_option('rcb_settings_options'));wp-callmeback.php:989
unserialize$get_recaptcha_details = unserialize(get_option('rcb_recaptcha_options'));wp-callmeback.php:990
unserialize$get_color_picker = unserialize(get_option('rcb_settings_options_picker'));wp-callmeback.php:991
unserialize$get_option_details = unserialize(get_option('rcb_recaptcha_options'));wp-callmeback.php:1410
unserialize$get_option_details = unserialize(get_option('rcb_settings_options_picker'));wp-callmeback.php:1460
unserialize$get_recaptcha_details = unserialize(get_option('rcb_recaptcha_options'));wp-callmeback.php:1461

SQL Query Safety

50% prepared22 total queries

Output Escaping

17% escaped144 total outputs
Data Flows · Security
12 unsanitized

Data Flow Analysis

12 flows12 with unsanitized paths
search_box (class\class-wp-list-table-copy.php:282)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Sitewise Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 13
actionadmin_footerclass\class-wp-list-table-copy.php:115
actionadmin_headclass\class-wpg-besttime-list-table.php:44
actionadmin_headclass\class-wpg-callback-list-table.php:49
actionadmin_headclass\class-wpg-dropdownoptions-list-table.php:44
actionadmin_menuwp-callmeback.php:137
actionwp_enqueue_scriptswp-callmeback.php:138
actionadmin_enqueue_scriptswp-callmeback.php:139
actionadmin_post_submit-callback-settings-formwp-callmeback.php:140
actionadmin_post_submit-callback-settings-optionswp-callmeback.php:141
actionadmin_post_submit-besttime-formwp-callmeback.php:142
actionadmin_post_submit-dropdownoptions-formwp-callmeback.php:143
actionadmin_post_submit-recaptcha-formwp-callmeback.php:144
actionwidgets_initwp-callmeback.php:563
Maintenance & Trust

Sitewise Maintenance & Trust

Maintenance Signals

WordPress version tested7.0.2
Last updatedJun 13, 2026
PHP min version7.4
Downloads23K

Community Trust

Rating100/100
Number of ratings1
Active installs30
Developer Profile

Sitewise Developer Profile

jody nesbitt

4 plugins · 10K total installs

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

How We Detect Sitewise

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/wp-call-me-back/css/wp-callmeback.css/wp-content/plugins/wp-call-me-back/css/colpick.css/wp-content/plugins/wp-call-me-back/js/colpick.js/wp-content/plugins/wp-call-me-back/style.css
Script Paths
/wp-content/plugins/wp-call-me-back/js/colpick.js
Version Parameters
wp-call-me-back/style.css?ver=wp-callmeback-stylewpgcallmeback-style

HTML / DOM Fingerprints

CSS Classes
nav-tab-wrappernav-tabnav-tab-active
Data Attributes
data-sitekey
JS Globals
grecaptcha
FAQ

Frequently Asked Questions about Sitewise