LiveActive security incident?Get immediate response
CVE Record

CVE-2023-45647: WordPress Constant Contact Forms by MailMunch Plugin <= 2.0.10 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in MailMunch Constant Contact Forms by MailMunch plugin <= 2.0.10 versions.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a medium-severity CSRF issue in the WordPress Constant Contact Forms by MailMunch plugin. If a site uses version 2.0.10 or earlier, a user could be tricked into performing an unintended action in the plugin context. The sources do not state active exploitation or a confirmed fixed version.

Executive priority

Handle this as a moderate WordPress hygiene issue. It is not supported as actively exploited by the provided sources, but affected internet-facing sites should be inventoried and remediated because CSRF can cause unauthorized actions through trusted users.

Technical view

CVE-2023-45647 is CWE-352 affecting Constant Contact Forms by MailMunch versions up to 2.0.10. CVSS 3.1 is 5.4: network-reachable, low complexity, no attacker privileges, user interaction required, with low integrity and availability impact and no confidentiality impact.

Likely exposure

Exposure is limited to WordPress sites with the Constant Contact Forms by MailMunch plugin installed at version 2.0.10 or earlier. Organizations without this plugin are not affected based on the provided sources.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. The attack requires user interaction, consistent with CSRF risk, but the bundle does not provide operational details or confirmed real-world abuse.

Researcher notes

The source bundle identifies CSRF only at a high level and does not include exploit details, vulnerable endpoints, nonce behavior, or a fixed release. Validation should focus on asset inventory, installed plugin version, and vendor advisory tracking.

Mitigation direction

  • Inventory WordPress sites for the affected MailMunch plugin.
  • Flag installed plugin versions 2.0.10 or earlier for review.
  • Check vendor, WordPress, or Patchstack guidance for a fixed version.
  • Disable or remove the plugin where it is not business-critical.
  • Prioritize remediation on externally managed or high-value WordPress sites.

Validation and detection

  • Confirm whether package constant-contact-forms-by-mailmunch is installed.
  • Record the installed version on each WordPress site.
  • Treat version 2.0.10 or earlier as potentially affected.
  • Review site change history for unexpected plugin-related changes.
  • Document compensating controls if immediate removal is not possible.
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-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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-45647 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.4 (3.1)
Known Exploited
No
Published

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

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.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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
MailMunchConstant Contact Forms by MailMunchconstant-contact-forms-by-mailmunch, n/aunaffected
Weakness

CWE details

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

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.