dbcve.org
Wordpress Email Template DesignerWordPress extension · Codemiq

CVE-2021-20779

HIGH · 8.8 CVSS v3.1 Published 2021-07-07
Fix available
A fix is available. Upgrade to 3.0.8 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 WordPress Email Template Designer - WP HTML Mail versions prior to 3.0.8 allows remote attackers to hijack the authentication of administrators via unspecified vectors.

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 WordPress Email Template Designer - WP HTML Mail plugin allows remote attackers to forge requests on behalf of authenticated administrators, potentially hijacking their session to modify email template settings.

MitigationUpgrade to WP HTML Mail version 3.0.8 or later which includes anti-CSRF token protection. If immediate patching is not possible, implement additional validation such as checking Origin/Referer headers and implementing a robust CSRF token mechanism.

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
Wordpress Email Template DesignerWordPress extension
Affected:< 3.0.8

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 WP HTML Mail plugin is installed
    Log into WordPress admin panel, navigate to Plugins > Installed Plugins, and search for 'WP HTML Mail' or 'Email Template Designer' by Codemiq
    Affected if The plugin is listed as installed and active in the WordPress plugins directory
  2. Determine the installed plugin version
    In the Plugins list, locate WP HTML Mail and view the version number displayed below the plugin name, or check the plugin's main PHP file header for the Version field
    Affected if The displayed version number is lower than 3.0.8 (e.g., 3.0.7, 3.0.6, etc.)
  3. Inspect plugin code for CSRF token protection
    Examine the plugin's admin form handlers (typically in files like class-*.php or admin/*.php) for presence of nonce verification using wp_verify_nonce or check_ajax_referer when processing email template settings
    Affected if No nonce or token verification is found in form processing code for email template modifications, indicating missing CSRF safeguards
  4. Check for Origin/Referer header validation
    Review the plugin's form submission handlers to verify if HTTP Origin or Referer headers are validated before processing admin actions
    Affected if No header-based validation is implemented in the plugin's request handling logic

The environment is affected if the WP HTML Mail plugin version is below 3.0.8 and the plugin code lacks anti-CSRF token (nonce) verification for email template modification forms.

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 3.0.8 or later
Fixed in 3.0.8
Interim mitigation

Upgrade to WP HTML Mail version 3.0.8 or later which includes anti-CSRF token protection. If immediate patching is not possible, implement additional validation such as checking Origin/Referer headers and implementing a robust CSRF token mechanism.

Recommended fix High confidence

3.0.8

  1. 1. Back up your WordPress site and database before making any changes
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Find 'WordPress Email Template Designer' (WP HTML Mail) in the plugin list
  5. 5. If an update is available, click 'Update Now' to update to version 3.0.8 or later
  6. 6. Alternatively, navigate to Dashboard > Updates to check for and apply available updates
  7. 7. Verify the plugin version after update to confirm version 3.0.8 or higher is installed

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

Fix this in Wordpress Email Template Designer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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