
Spam Protect for Contact Form 7 Security & Risk Analysis
wordpress.org/plugins/wp-contact-form-7-spam-blockerSpam Protect for Contact-Form7 protects from spam and bots. Customize defense strategies and monitor blocked attempts. Protect your time effectively!
Is Spam Protect for Contact Form 7 Safe to Use in 2026?
Generally Safe
Score 100/100Spam Protect for Contact Form 7 has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.
The plugin 'wp-contact-form-7-spam-blocker' version 1.2.10 exhibits a generally strong security posture based on the provided static analysis. The absence of any CVEs in its history and the reported zero critical or high severity vulnerabilities indicate a commitment to secure coding practices over time. The code analysis reveals a clean slate regarding dangerous functions and external HTTP requests, and all SQL queries are properly prepared. Furthermore, output escaping is largely effective, with 94% of outputs being properly escaped. This suggests a mature and well-maintained plugin.
However, a significant concern arises from the taint analysis, which identified three flows with unsanitized paths. While these did not reach a critical or high severity level, the presence of unsanitized paths, even if mitigated by other factors not detailed here, represents a potential area of weakness. The plugin also lacks capability checks and nonce checks entirely, which, coupled with zero unprotected AJAX handlers or REST API routes, implies that these entry points are either not used or are protected by other means not immediately apparent in this report. The file operations without context for their security implications also warrant a minor caution.
In conclusion, the plugin is largely secure, with a strong track record and good coding practices in place. The primary areas of concern are the identified unsanitized paths in the taint analysis and the complete absence of capability and nonce checks. These factors, while not currently manifesting as critical vulnerabilities, should be monitored and addressed for a more robust security posture.
Key Concerns
- Taint flows with unsanitized paths found
- No capability checks
- No nonce checks
- File operations present without detailed security context
Spam Protect for Contact Form 7 Security Vulnerabilities
Spam Protect for Contact Form 7 Code Analysis
Output Escaping
Data Flow Analysis
Spam Protect for Contact Form 7 Attack Surface
WordPress Hooks 13
Maintenance & Trust
Spam Protect for Contact Form 7 Maintenance & Trust
Maintenance Signals
Community Trust
Spam Protect for Contact Form 7 Alternatives
No alternatives data available yet.
Spam Protect for Contact Form 7 Developer Profile
1 plugin · 10K total installs
How We Detect Spam Protect for Contact Form 7
Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.
Asset Fingerprints
/wp-content/plugins/wp-contact-form-7-spam-blocker/admin/css/style.css/wp-content/plugins/wp-contact-form-7-spam-blocker/admin/js/spcf7-admin.js/wp-content/plugins/wp-contact-form-7-spam-blocker/public/css/spcf7-public.css/wp-content/plugins/wp-contact-form-7-spam-blocker/public/js/spcf7-public.jswp-contact-form-7-spam-blocker/admin/css/style.css?ver=wp-contact-form-7-spam-blocker/admin/js/spcf7-admin.js?ver=wp-contact-form-7-spam-blocker/public/css/spcf7-public.css?ver=wp-contact-form-7-spam-blocker/public/js/spcf7-public.js?ver=HTML / DOM Fingerprints
spcf7-noticeblocker-7-settingblocker-7-setting-smallmain-wrap<!-- If this file is called directly, abort. --><!-- The code that runs during plugin activation. --><!-- The code that runs during plugin deactivation. --><!-- The core plugin class that is used to define internationalization, admin-specific hooks, and public-facing site hooks. -->+9 moreid="wpcf7-block-email-list-id"id="wpcf7-block-email-domain-id"id="wpcf7-block-top-domain-id"id="wpcf7-protected-fields-id"id="wpcf7-block-words-id"id="wpcf7-block-shortlinks-id"+12 morewindow.spcf7_object