CF7 Telefone Security & Risk Analysis

wordpress.org/plugins/cf7-telefone

Plugin do WordPress que adiciona máscara nos campos de telefone do Contact Form 7

20 active installs v1.0 PHP + WP 3.0+ Updated Apr 13, 2016
cf7-maskcontact-form-telcontact-form-telefonemascara-telefonetelefone-cf7
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is CF7 Telefone Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 9yr ago
Risk Assessment

Based on the static analysis, the "cf7-telefone" v1.0 plugin exhibits a strong security posture with no identified dangerous functions, SQL injection vulnerabilities, or output escaping issues. The absence of file operations and external HTTP requests further reduces the potential attack vectors. Crucially, there are no identified flows with unsanitized paths in the taint analysis, indicating a generally clean code base regarding data handling.

The vulnerability history is also clean, with no known CVEs recorded for this plugin. This lack of past vulnerabilities suggests a commitment to security by the developers or a lack of discovery, which is a positive indicator. However, the complete absence of entry points such as AJAX handlers, REST API routes, shortcodes, and cron events is unusual for a plugin and could indicate that it is either a very simple utility or perhaps not fully functional in a way that would expose it to typical WordPress vulnerabilities. It also means that while there are no *identified* vulnerabilities within these areas, the lack of any such areas to analyze is a weakness in terms of assessment scope.

In conclusion, the plugin appears to be built with good security practices in mind, showing no direct code-level weaknesses. The main concern is the limited attack surface analysis, which might be due to its specific functionality or design, rather than a deliberate security measure. While currently secure based on the provided data, the lack of exploitable entry points makes a comprehensive security assessment challenging.

Key Concerns

  • Zero identified entry points for analysis
  • Zero nonce checks found
  • Zero capability checks found
Vulnerabilities
None known

CF7 Telefone Security Vulnerabilities

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

CF7 Telefone Code Analysis

Dangerous Functions
0
Raw SQL Queries
0
0 prepared
Unescaped Output
0
0 escaped
Nonce Checks
0
Capability Checks
0
File Operations
0
External Requests
0
Bundled Libraries
0
Attack Surface

CF7 Telefone Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 1
actionwp_enqueue_scriptscf7-telefone.php:16
Maintenance & Trust

CF7 Telefone Maintenance & Trust

Maintenance Signals

WordPress version tested4.5.33
Last updatedApr 13, 2016
PHP min version
Downloads2K

Community Trust

Rating20/100
Number of ratings4
Active installs20
Developer Profile

CF7 Telefone Developer Profile

lucascaires

2 plugins · 2K total installs

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

How We Detect CF7 Telefone

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/cf7-telefone/js/cf7-telefone.js
Script Paths
/wp-content/plugins/cf7-telefone/js/cf7-telefone.js
Version Parameters
cf7-telefone/js/cf7-telefone.js?ver=

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about CF7 Telefone