dbcve.org
Kadence Woocommerce Email DesignerWordPress extension · Kadencewp

CVE-2023-47186

HIGH · 8.8 CVSS v3.1 Published 2023-11-06
Fix available
A fix is available. Upgrade to after 1.5.11 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Kadence WP Kadence WooCommerce Email Designer plugin <= 1.5.11 versions.

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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Kadence WooCommerce Email Designer plugin allows attackers to trick authenticated administrators into performing unintended actions such as modifying email templates or plugin settings. The vulnerability exists because the plugin does not properly validate anti-CSRF tokens on form submissions and AJAX requests.

MitigationUpdate the Kadence WooCommerce Email Designer plugin to version 1.5.12 or later, which includes proper nonce verification for state-changing requests.

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
Kadence Woocommerce Email DesignerWordPress extension
Affected:<= 1.5.11

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Verify Kadence WooCommerce Email Designer plugin is installed
    In WordPress admin, navigate to Plugins > Installed Plugins and look for 'Kadence WooCommerce Email Designer' in the list. Alternatively, check the plugin files in /wp-content/plugins/ for the kadence-woocommerce-email-designer directory.
    Affected if Plugin is not found in the installation
  2. Confirm the plugin is active
    In WordPress admin > Plugins, check if 'Kadence WooCommerce Email Designer' shows as 'Active' under the plugin status.
    Affected if Plugin is not active
  3. Identify the installed plugin version
    In WordPress admin > Plugins, click on the plugin name to view details, or check the plugin header in /wp-content/plugins/kadence-woocommerce-email-designer/kadence-woocommerce-email-designer.php for the 'Version' field.
    Affected if Version number cannot be determined
  4. Compare version against affected range
    Compare the installed version number to the affected range: any version 1.5.11 or earlier is vulnerable.
    Affected if Installed version is 1.5.11 or lower
  5. Confirm WooCommerce is active
    In WordPress admin > Plugins, verify WooCommerce is installed and active, as this plugin extends WooCommerce email functionality.
    Affected if WooCommerce is not active

The environment is affected if the Kadence WooCommerce Email Designer plugin is installed, active, and running version 1.5.11 or earlier.

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 1.5.11
Interim mitigation

Update the Kadence WooCommerce Email Designer plugin to version 1.5.12 or later, which includes proper nonce verification for state-changing requests.

Recommended fix Moderate confidence

1.5.12 or latest available version

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Kadence WooCommerce Email Designer' in the plugin list
  4. Check if an update is available and click 'Update Now'
  5. Alternatively, download the latest version from the WordPress plugin repository
  6. Deactivate the current plugin version
  7. Delete the current plugin files
  8. Upload and install the new version

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

Fix this in Kadence Woocommerce Email Designer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-47186 — 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-47186 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