Phone Button Security & Risk Analysis

wordpress.org/plugins/phone-button

Simple plugin that allow you add call phone button to your wordpress site

700 active installs v2.1.2 PHP 5.2.4+ WP 5.0+ Updated Dec 10, 2025
click-phoneclick-to-callcontact-buttonphone-button
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Phone Button Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs Updated 3mo ago
Risk Assessment

The "phone-button" plugin version 2.1.2 demonstrates a strong security posture based on the provided static analysis. It correctly implements nonce and capability checks for its AJAX entry points, and all SQL queries are secured with prepared statements, indicating good development practices regarding common WordPress vulnerabilities.

Concerns are primarily related to output escaping. With 76% of outputs properly escaped, there's still a 24% portion that is not, which could potentially lead to cross-site scripting (XSS) vulnerabilities if user-supplied data is handled improperly. The absence of any taint flows or dangerous functions is a positive sign, suggesting that the plugin is not directly introducing critical vulnerabilities in these areas. The clean vulnerability history with zero recorded CVEs further bolsters confidence in its current security state.

Overall, the plugin appears well-developed from a security perspective, with the main area for improvement being the consistent and comprehensive escaping of all outputs to mitigate potential XSS risks. The strong foundation in authentication and SQL security, combined with a lack of historical vulnerabilities, makes this a relatively low-risk plugin, provided the unescaped outputs do not handle sensitive user input.

Key Concerns

  • Unescaped output detected (24%)
Vulnerabilities
None known

Phone Button Security Vulnerabilities

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

Phone Button Code Analysis

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

Output Escaping

76% escaped98 total outputs
Attack Surface

Phone Button Attack Surface

Entry Points2
Unprotected0

AJAX Handlers 2

authwp_ajax_yydev_phone_btn_stop_notice_forevernotices.php:62
authwp_ajax_yydev_phone_btn_stop_notice_for_nownotices.php:84
WordPress Hooks 6
actionwp_headinclude\front-end-output.php:166
actionwp_footerinclude\front-end-output.php:207
actionadmin_menuindex.php:51
filterplugin_action_linksindex.php:69
filterplugin_action_linksindex.php:75
actionadmin_noticesnotices.php:274
Maintenance & Trust

Phone Button Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.4
Last updatedDec 10, 2025
PHP min version5.2.4
Downloads7K

Community Trust

Rating100/100
Number of ratings1
Active installs700
Developer Profile

Phone Button Developer Profile

yydevelopment

11 plugins · 51K total installs

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

How We Detect Phone Button

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/phone-button/include/style.php/wp-content/plugins/phone-button/include/scripts.php/wp-content/plugins/phone-button/include/admin-output.php/wp-content/plugins/phone-button/include/install.php/wp-content/plugins/phone-button/include/functions.php/wp-content/plugins/phone-button/notices.php/wp-content/plugins/phone-button/include/front-end-output.php

HTML / DOM Fingerprints

CSS Classes
yydev-phone-button
Data Attributes
data-activevalue
FAQ

Frequently Asked Questions about Phone Button