LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47186: WordPress Kadence WooCommerce Email Designer Plugin <= 1.5.11 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Kadence WP Kadence WooCommerce Email Designer plugin <= 1.5.11 versions.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-47186 is a medium-severity CSRF issue in the Kadence WooCommerce Email Designer WordPress plugin through 1.5.11. A successful attack would likely require tricking an authenticated site user into making an unintended request. The published data indicates limited integrity impact, not data theft or service outage.

Executive priority

Treat this as a normal-priority WordPress plugin remediation unless the plugin manages business-critical store communications or many admins use shared browsing environments. It is not described as actively exploited, but affected sites should be updated or reviewed through vendor guidance.

Technical view

The CVE describes CWE-352 in package kadence-woocommerce-email-designer, affecting Kadence WooCommerce Email Designer <= 1.5.11. CVSS 3.1 is 4.3: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, low integrity impact, no confidentiality or availability impact.

Likely exposure

Exposure is likely limited to WordPress/WooCommerce sites with Kadence WooCommerce Email Designer installed at version 1.5.11 or earlier. Sites not using the plugin are not indicated as exposed by the provided sources.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. The CVSS vector requires user interaction, consistent with CSRF, and indicates only low integrity impact. Exact vulnerable actions are not described in the provided evidence.

Researcher notes

The public bundle identifies the weakness class, affected plugin, version ceiling, CVSS vector, and Patchstack reference. It does not provide vulnerable endpoint details, proof-of-concept status, a fixed version, or confirmed exploit activity, so validation should stay inventory- and advisory-driven.

Mitigation direction

  • Inventory WordPress sites for the Kadence WooCommerce Email Designer plugin.
  • Check installed plugin versions and prioritize versions 1.5.11 or earlier.
  • Follow Kadence WP or Patchstack guidance for the fixed version or workaround.
  • Limit WordPress admin access to trusted users while remediation is pending.
  • Remind admins not to open untrusted links while logged into WordPress.

Validation and detection

  • Confirm whether the plugin package kadence-woocommerce-email-designer is installed.
  • Record the exact installed version on each WordPress instance.
  • Compare findings against the affected range of 1.5.11 or earlier.
  • Review vendor or Patchstack advisory details before closing remediation.
  • Check recent WooCommerce email template/settings changes for unexpected modifications.
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-47186 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-47186Attack 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
Kadence WPKadence WooCommerce Email Designerkadence-woocommerce-email-designer, 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.