LiveActive security incident?Get immediate response
CVE Record

CVE-2023-45748: WordPress MailChimp Forms by MailMunch Plugin <= 3.1.4 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in MailMunch MailChimp Forms by MailMunch plugin <= 3.1.4 versions.

MediumCVSS 4.3Not 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 MailChimp Forms by MailMunch plugin up to 3.1.4. An attacker would need to trick a user into interacting with a crafted page or link. The documented impact is limited integrity impact, with no confidentiality or availability impact in the provided CVSS data.

Executive priority

Treat as a scheduled remediation item unless the plugin supports critical lead-generation workflows or is broadly deployed. The main business risk is unauthorized configuration or content change through user deception, not data theft or service outage based on supplied evidence.

Technical view

CVE-2023-45748 is CWE-352 affecting the MailMunch MailChimp Forms by MailMunch WordPress plugin <= 3.1.4. CVSS 3.1 is 4.3, vector AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N. The source bundle does not provide request details, affected endpoints, proof of exploitation, or a fixed version.

Likely exposure

Exposure is limited to WordPress sites using MailChimp Forms by MailMunch versions up to 3.1.4. Sites without this plugin, or not on affected versions, are not indicated as exposed by the provided sources.

Exploitation context

The source bundle does not indicate active exploitation, and CISA KEV status is false. The CVSS vector requires user interaction and no attacker privileges. No exploit procedure or observed campaign is documented in the supplied sources.

Researcher notes

The record is sparse. Patchstack and CVE identify CSRF in versions <= 3.1.4, but the source bundle lacks endpoint-level details, exploit conditions beyond CVSS UI:R, and a named fixed version. Avoid asserting active exploitation or specific impact paths without additional vendor evidence.

Mitigation direction

  • Inventory WordPress sites for the MailChimp Forms by MailMunch plugin.
  • Identify installations running version 3.1.4 or earlier.
  • Check vendor, WordPress.org, or Patchstack guidance for a fixed release.
  • Update when a vendor-supported fixed version is available.
  • Disable or remove the plugin where it is not business-critical.

Validation and detection

  • Confirm plugin name and version from WordPress administration or asset inventory.
  • Map affected sites to business owners and public exposure.
  • Review vendor or Patchstack records for current remediation guidance.
  • Check administrative change logs for unexpected MailMunch form or configuration changes.
  • Document compensating controls if an update is unavailable.
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-45748 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
4.3 (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: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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2023-45748Attack 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: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
MailMunchMailChimp Forms by MailMunchmailchimp-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.