Overtok Call Conversion Security & Risk Analysis

wordpress.org/plugins/overtok

Convert inbound calls into additional actions. Connect business calls from any digital asset with an outstanding on-site visual journey that converts …

10 active installs v0.5 PHP 5.4+ WP 3.3+ Updated Unknown
call-trackingchatmessagingvideovoice
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Overtok Call Conversion Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs
Risk Assessment

The static analysis of the "overtok" v0.5 plugin reveals a generally strong security posture with a limited attack surface and no immediate critical vulnerabilities detected.

The absence of AJAX handlers, REST API routes, shortcodes, and cron events significantly reduces the plugin's exposure to external attacks. The code signals also indicate a positive trend, with no dangerous functions identified, all SQL queries utilizing prepared statements, and no file operations or external HTTP requests. The presence of a nonce check is a good practice. However, the low percentage of properly escaped output (67%) is a potential concern, as even a few unescaped outputs could lead to cross-site scripting (XSS) vulnerabilities.

The plugin has no recorded vulnerability history, which is a positive indicator. The lack of known CVEs and past common vulnerability types suggests that the developers have either been diligent in addressing security or the plugin has not been a significant target for attackers. Overall, the plugin appears to be built with security in mind, but the output escaping should be reviewed to ensure all dynamic data is properly sanitized before being displayed to users.

Key Concerns

  • Low percentage of properly escaped output
Vulnerabilities
None known

Overtok Call Conversion Security Vulnerabilities

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

Overtok Call Conversion Code Analysis

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

Output Escaping

67% escaped6 total outputs
Data Flows
All sanitized

Data Flow Analysis

2 flows
setting_page (overtok-init.php:129)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Overtok Call Conversion Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 6
actionadmin_menuovertok-init.php:32
actionadmin_initovertok-init.php:33
actioninitovertok-init.php:34
actionwp_footerovertok-init.php:81
actionwp_headovertok-init.php:84
filterthe_contentovertok-init.php:87
Maintenance & Trust

Overtok Call Conversion Maintenance & Trust

Maintenance Signals

WordPress version tested4.9.29
Last updatedUnknown
PHP min version5.4
Downloads1K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Overtok Call Conversion Developer Profile

wpdugi

1 plugin · 10 total installs

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

How We Detect Overtok Call Conversion

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

Asset Fingerprints

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Overtok Call Conversion