LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52208: WordPress Constant Contact Forms Plugin <= 2.4.2 is vulnerable to Sensitive Data Exposure

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.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Constant Contact Forms for WordPress through version 2.4.2 can expose sensitive information to someone who should not have it. The reported impact is limited to confidentiality, not system takeover or service disruption, but exposed form or log data can still create privacy, fraud, and incident-response obligations.

Executive priority

Prioritize this as a near-term privacy and data-exposure issue for internet-facing WordPress sites. It is not rated critical, but unauthenticated access and possible sensitive form data exposure justify prompt inventory, remediation planning, and log review.

Technical view

CVE-2023-52208 is a CWE-200 sensitive information exposure issue in the WordPress Constant Contact Forms plugin through 2.4.2. The Patchstack reference describes exposure via a log file. CVSS 3.1 is 5.3 with network access, low complexity, no privileges, and no user interaction required.

Likely exposure

Exposure is most likely on WordPress sites running Constant Contact Forms version 2.4.2 or earlier. The provided sources do not identify affected hosting configurations, exact exposed data types, or whether newer versions contain a fix.

Exploitation context

The source bundle does not show active exploitation, and this CVE is not marked as KEV. CVSS indicates unauthenticated network reachability, so public WordPress sites with the affected plugin should still be treated as externally exposed until validated.

Researcher notes

Evidence is limited to CVE metadata and Patchstack’s vulnerability entry. The bundle does not provide exploit details, data fields exposed, affected paths, or a named fixed version. Avoid assuming compromise without logs or other evidence.

Mitigation direction

  • Inventory WordPress sites for the Constant Contact Forms plugin.
  • Identify any installation running version 2.4.2 or earlier.
  • Check vendor and Patchstack guidance for the fixed or recommended version.
  • Update, disable, or remove affected installations based on validated vendor guidance.
  • Restrict public access to sensitive logs where operationally possible.
  • Review retained logs for unnecessary sensitive information.

Validation and detection

  • Confirm plugin name and version on each WordPress instance.
  • Check whether version 2.4.2 or earlier is present.
  • Review web server logs for access to plugin-related log files.
  • Verify no sensitive plugin logs are publicly reachable.
  • Document affected sites, remediation status, and residual exposure.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-52208 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2023-52208Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Constant ContactConstant Contact Formsconstant-contact-forms, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.