Simple Constant Contact Security & Risk Analysis

wordpress.org/plugins/simple-constant-contact

Simple Wordpress Constant Contact Plugin to take name and email and allow to send that information straight to Constant Contact

20 active installs v1.1 PHP + WP 3.8+ Updated Apr 10, 2016
constantconstant-contactcontactnewsletterwordpress-org
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Simple Constant Contact Safe to Use in 2026?

Generally Safe

Score 85/100

Simple Constant Contact has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 10yr ago
Risk Assessment

The 'simple-constant-contact' plugin version 1.1 presents a generally good security posture based on the provided static analysis. The absence of dangerous functions, raw SQL queries, file operations, and the high percentage of properly escaped outputs are strong indicators of secure coding practices. The plugin also has no recorded vulnerabilities, which is a significant positive sign for its overall reliability and security. However, there are a few areas that warrant attention. The presence of an external HTTP request, while not inherently insecure, could be a potential vector for issues if not handled with proper validation and sanitization. Additionally, the complete lack of nonce checks and capability checks across all entry points is a notable weakness. While the current attack surface is small and has no direct unprotected points, the absence of these fundamental WordPress security mechanisms leaves it vulnerable to various attacks, such as Cross-Site Request Forgery (CSRF) or unauthorized actions, should any new entry points be introduced or existing ones become exploitable.

Key Concerns

  • Missing nonce checks on entry points
  • Missing capability checks on entry points
  • External HTTP request without context
Vulnerabilities
None known

Simple Constant Contact Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Version History

Simple Constant Contact Release Timeline

No version history available.
Code Analysis
Analyzed Mar 16, 2026

Simple Constant Contact Code Analysis

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

Output Escaping

90% escaped10 total outputs
Attack Surface

Simple Constant Contact Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[simpleCC] simple_constant_contact.php:321
WordPress Hooks 4
actionadmin_initsimple_constant_contact.php:319
actioninitsimple_constant_contact.php:320
actionadmin_menusimple_constant_contact.php:322
actionwp_enqueue_scriptssimple_constant_contact.php:325
Maintenance & Trust

Simple Constant Contact Maintenance & Trust

Maintenance Signals

WordPress version tested4.4.34
Last updatedApr 10, 2016
PHP min version
Downloads3K

Community Trust

Rating66/100
Number of ratings3
Active installs20
Developer Profile

Simple Constant Contact Developer Profile

Ashton Paul

1 plugin · 20 total installs

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

How We Detect Simple Constant Contact

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

Asset Fingerprints

HTML / DOM Fingerprints

CSS Classes
simpleCC-options-form
HTML Comments
<!-- display form in admin menu --><!-- WordPress 4.3.1 -->
JS Globals
window.simpleCC
Shortcode Output
<form method="post" class="simpleCC-form"><input type="hidden" name="simpleCC_fname" value=""><input type="hidden" name="simpleCC_lname" value=""><input type="hidden" name="simpleCC_email" value="">
FAQ

Frequently Asked Questions about Simple Constant Contact