dbcve.org
Creative MailWordPress extension · Constantcontact

CVE-2022-40687

HIGH · 8.8 CVSS v3.1 Published 2022-11-18
Fix available
A fix is available. Upgrade to 1.6.0 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 Creative Mail plugin <= 1.5.4 on WordPress.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Creative Mail plugin for WordPress allows remote attackers to induce authenticated administrators to perform unintended actions by tricking them into clicking malicious links or visiting crafted webpages, exploiting the lack of proper request origin validation in the plugin's administrative functions.

MitigationUpdate Creative Mail plugin to a version newer than 1.5.4. If no patched version is available, implement WordPress nonces (anti-CSRF tokens) on all state-changing actions and enforce SameSite cookie attributes.

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
Creative MailWordPress extension
Affected:< 1.6.0

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 Creative Mail plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, or check the /wp-content/plugins/ directory for the 'creative-mail' folder
    Affected if The Creative Mail plugin by Constant Contact is present in the WordPress installation
  2. Check installed version of Creative Mail
    In WordPress admin, go to Plugins > Installed Plugins and look at the version number listed under the Creative Mail plugin, or read the main plugin file header for the 'Version' tag
    Affected if The reported version is below 1.6.0 (vulnerable versions are < 1.6.0)
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify the Creative Mail plugin shows as 'Active'
    Affected if The plugin is active and administrative functions are exposed to authenticated administrators
  4. Identify exposed admin actions
    Review plugin source code in /wp-content/plugins/creative-mail/ for form handlers and admin action hooks (add_action with 'admin_init' or 'admin_post_') that lack nonce verification or origin validation
    Affected if Administrative action handlers exist without proper CSRF protections (nonce checks or request origin validation)

You are affected if the Creative Mail plugin is installed, active, and running version 1.5.4 or lower, exposing unauthenticated CSRF vectors against authenticated administrators.

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

Update Creative Mail plugin to a version newer than 1.5.4. If no patched version is available, implement WordPress nonces (anti-CSRF tokens) on all state-changing actions and enforce SameSite cookie attributes.

Recommended fix High confidence

Creative Mail 1.6.0 or higher

  1. Backup your WordPress database and files before making any changes
  2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. Locate Creative Mail plugin in the list
  4. Check if current version is below 1.6.0
  5. If vulnerable, click 'Update Now' or download version 1.6.0+ from WordPress plugin repository
  6. Verify the update was successful by checking the plugin version after updating

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

Fix this in Creative Mail 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-40687 — 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-40687 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