dbcve.org
Constant Contact FormsWordPress extension · Constantcontact

CVE-2023-52208

HIGH · 7.5 CVSS v3.1 Published 2024-01-08
Fix available
A fix is available. Upgrade to after 2.4.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Constant Contact Constant Contact Forms.This issue affects Constant Contact Forms: from n/a through 2.4.2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · low confidence

Information disclosure vulnerability in Constant Contact Forms plugin allowing unauthorized access to sensitive data. The specific exposure mechanism is not detailed in the advisory, but the CVSS 7.5 score indicates significant risk of exposed credentials, user data, or configuration details.

MitigationUpdate to the latest version of Constant Contact Forms (beyond 2.4.2) if available. If no patched version exists, disable the plugin until a fix is released and review access logs for indicators of compromise.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Constant Contact FormsWordPress extension
Affected:<= 2.4.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Constant Contact Forms plugin installation
    Check the WordPress plugins directory at wp-content/plugins/ for a folder named 'constant-contact-forms' or 'constantcontact', or view the installed plugins list in WordPress admin under Plugins > Installed Plugins
    Affected if The plugin folder exists in the WordPress installation
  2. Identify the installed version number
    Open the main plugin file (usually constant-contact-forms.php) and locate the version header in the plugin comments, or check the version column in Plugins > Installed Plugins in WordPress admin
    Affected if The version number displayed is 2.4.2 or lower
  3. Verify the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and confirm the Constant Contact Forms plugin has an 'Active' status, or query the wp_options table for option_name='active_plugins'
    Affected if The plugin is currently activated on the site
  4. Check for unauthorized access indicators
    Review web server access logs and WordPress audit logs for unusual requests to plugin endpoints, especially API calls, form submission handlers, or admin-ajax.php actions originating from unexpected IP addresses
    Affected if Log entries show excessive or anomalous requests to plugin-related URLs from unknown sources

The environment is affected if the Constant Contact Forms plugin version is 2.4.2 or lower and the plugin is installed and active on the WordPress site.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.4.2
Interim mitigation

Update to the latest version of Constant Contact Forms (beyond 2.4.2) if available. If no patched version exists, disable the plugin until a fix is released and review access logs for indicators of compromise.

Recommended fix Moderate confidence

Update to the latest version of Constant Contact Forms (check WordPress plugin repository for post-2.4.2 release)

  1. Check the WordPress admin dashboard for the Constant Contact Forms plugin update notification
  2. Navigate to Plugins > Installed Plugins > Constant Contact Forms
  3. If an update is available, click 'Update Now' to install the latest version
  4. After updating, verify the plugin version number matches or exceeds the fixed release
  5. Review the plugin's changelog on the WordPress plugin repository to confirm the security fix is included

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Constant Contact Forms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-52208 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-52208 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data