dbcve.org
Email Templates Customizer And DesignerApplication · Wpexperts

CVE-2022-47181

HIGH · 8.8 CVSS v3.1 Published 2023-11-07
Fix available
A fix is available. Upgrade to after 1.4.2 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 wpexpertsio Email Templates Customizer and Designer for WordPress and WooCommerce email-templates allows Cross Site Request Forgery.This issue affects Email Templates Customizer and Designer for WordPress and WooCommerce: from n/a through 1.4.2.

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 Email Templates Customizer and Designer plugin for WordPress/WooCommerce allows attackers to induce authenticated administrators to perform unintended actions via forged requests, potentially leading to configuration changes or data modification.

MitigationImplement WordPress nonces (anti-CSRF tokens) on all form submissions and AJAX requests, and verify these nonces using check_admin_referer() or wp_verify_nonce() before processing any state-changing operations.

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
Email Templates Customizer And DesignerApplication
Affected:<= 1.4.2

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. Confirm plugin is installed
    Log into WordPress admin and go to Plugins > Installed Plugins. Look for 'Wpexperts Email Templates Customizer And Designer' in the list.
    Affected if Plugin is present and active in the WordPress installation
  2. Check installed version
    In the Plugins list, find the plugin and view the version number under the plugin name. Alternatively, open wp-content/plugins/wpexperts-email-templates-customizer-and-designer/wpexperts-email-templates-customizer.php and check the Version header in the plugin comments.
    Affected if Version is 1.4.2 or lower (any version up to and including 1.4.2)
  3. Verify nonce protection on admin actions
    Use browser developer tools or examine the plugin PHP source code to inspect form submissions and AJAX handlers in the plugin. Look for presence of wp_nonce_field(), wp_create_nonce(), check_admin_referer(), or wp_verify_nonce() calls before processing any state-changing operations.
    Affected if Forms or AJAX requests in the plugin lack nonce verification (no nonce field present and no nonce check in the handler)
  4. Confirm admin authentication is required
    Determine whether the vulnerable endpoints require administrator-level authentication by examining capability checks like current_user_can() or admin initialization in the plugin code.
    Affected if Authenticated administrators can be induced to perform actions via forged requests (the vulnerability applies to any admin action without CSRF protection)

User is affected if Wpexperts Email Templates Customizer And Designer plugin version 1.4.2 or lower is installed and the plugin's forms or AJAX handlers lack WordPress nonce verification.

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.4.2
Interim mitigation

Implement WordPress nonces (anti-CSRF tokens) on all form submissions and AJAX requests, and verify these nonces using check_admin_referer() or wp_verify_nonce() before processing any state-changing operations.

Recommended fix Moderate confidence

Version 1.4.3 or later (verify exact version through WordPress plugin repository or vendor)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'Email Templates Customizer And Designer' by wpexpertsio
  4. Check if an update is available and update to the latest version
  5. Alternatively, download the latest version from the official WordPress plugin repository and reinstall

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

Fix this in Email Templates Customizer And 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-2022-47181 — 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-2022-47181 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