Add-on SweetAlert Contact Form 7 Security & Risk Analysis

wordpress.org/plugins/addon-sweetalert-contact-form-7

Add SweetAlert2 script into Contact Form 7 submission process.

100 active installs v1.1.1 PHP 5.6+ WP + Updated Aug 1, 2020
cf7contact-formcontact-form-7sweet-alertsweetalert2
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Add-on SweetAlert Contact Form 7 Safe to Use in 2026?

Generally Safe

Score 85/100

Add-on SweetAlert Contact Form 7 has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 5yr ago
Risk Assessment

The plugin "addon-sweetalert-contact-form-7" v1.1.1 exhibits a strong security posture based on the provided static analysis. There are no identified dangerous functions, SQL queries are all prepared, and all output is properly escaped. The absence of file operations and external HTTP requests further reduces the attack surface. The plugin also has a clean vulnerability history with no recorded CVEs, suggesting a history of secure development practices.

However, a significant concern arises from the complete lack of nonce checks and capability checks across all entry points. While the static analysis reports zero unprotected entry points, this is misleading as the code signals indicate only one capability check overall. This absence of proper authentication and authorization mechanisms is a critical weakness. If any of the analyzed entry points (even though reported as zero) were to interact with sensitive data or functionality, the lack of these checks would expose the plugin to serious security risks such as unauthorized access and privilege escalation.

In conclusion, while the plugin demonstrates good practices in code hygiene and has no known vulnerabilities, the oversight in implementing robust authentication and authorization checks represents a substantial security gap. This lack of protection for potential entry points, even if currently unexploited or seemingly non-existent in static analysis, makes the plugin's security questionable and requires immediate attention.

Key Concerns

  • Missing nonce checks on potential entry points
  • Insufficient capability checks on entry points
Vulnerabilities
None known

Add-on SweetAlert Contact Form 7 Security Vulnerabilities

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

Add-on SweetAlert Contact Form 7 Code Analysis

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

Output Escaping

100% escaped20 total outputs
Attack Surface

Add-on SweetAlert Contact Form 7 Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 11
actionadmin_initaddon-sweetalert-contact-form-7.php:15
actionadmin_noticesaddon-sweetalert-contact-form-7.php:19
actionwp_headaddon-sweetalert-contact-form-7.php:63
actionwp_footeraddon-sweetalert-contact-form-7.php:118
actionwp_enqueue_scriptsaddon-sweetalert-contact-form-7.php:128
actionadmin_enqueue_scriptsaddon-sweetalert-contact-form-7.php:133
actionadmin_menuaddon-sweetalert-contact-form-7.php:163
actionadmin_initaddon-sweetalert-contact-form-7.php:187
actionplugins_loadedaddon-sweetalert-contact-form-7.php:205
actionwp_enqueue_scriptsincludes\functions.php:18
filterscript_loader_tagincludes\functions.php:21
Maintenance & Trust

Add-on SweetAlert Contact Form 7 Maintenance & Trust

Maintenance Signals

WordPress version tested5.5.18
Last updatedAug 1, 2020
PHP min version5.6
Downloads3K

Community Trust

Rating74/100
Number of ratings3
Active installs100
Developer Profile

Add-on SweetAlert Contact Form 7 Developer Profile

Camilo

5 plugins · 6K total installs

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

How We Detect Add-on SweetAlert Contact Form 7

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/addon-sweetalert-contact-form-7/style.css/wp-content/plugins/addon-sweetalert-contact-form-7/promise-polyfill.min.js/wp-content/plugins/addon-sweetalert-contact-form-7/sweetalert2.min.js/wp-content/plugins/addon-sweetalert-contact-form-7/swal-cf7-main.js
Script Paths
/wp-content/plugins/addon-sweetalert-contact-form-7/promise-polyfill.min.js/wp-content/plugins/addon-sweetalert-contact-form-7/sweetalert2.min.js/wp-content/plugins/addon-sweetalert-contact-form-7/swal-cf7-main.js
Version Parameters
/wp-content/plugins/addon-sweetalert-contact-form-7/style.css?ver=/wp-content/plugins/addon-sweetalert-contact-form-7/promise-polyfill.min.js?ver=/wp-content/plugins/addon-sweetalert-contact-form-7/sweetalert2.min.js?ver=/wp-content/plugins/addon-sweetalert-contact-form-7/swal-cf7-main.js?ver=

HTML / DOM Fingerprints

CSS Classes
swal-cf7__container
Data Attributes
name="swal_cf7_duration_success"name="swal_cf7_duration_error"name="swal_cf7_title_success"name="swal_cf7_title_error"
FAQ

Frequently Asked Questions about Add-on SweetAlert Contact Form 7