CVE-2026-3985
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 · uneditedThe Creative Mail – Easier WordPress & WooCommerce Email Marketing plugin for WordPress is vulnerable to SQL Injection via the 'checkout_uuid' parameter in all versions up to, and including, 1.6.9. This is due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query in the `has_checkout_consent()` method. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
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 confidenceThe Creative Mail WordPress plugin fails to properly sanitize the 'checkout_uuid' parameter before using it in an SQL query within the has_checkout_consent() method. This allows unauthenticated attackers to inject arbitrary SQL commands, potentially extracting sensitive data from the database.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Creative Mail plugin installation and versionIn WordPress admin, go to Plugins > Installed Plugins and find Creative Mail, or inspect the plugin header in wp-content/plugins/creative-mail-by-mailchimp/creative-mail.php for the Version: fieldAffected if Plugin is installed with version lower than 1.6.10
-
Confirm vulnerable method existsLocate the has_checkout_consent() method in the plugin files, typically in includes/ directory. Search for the method definition containing $checkout_uuid parameter and direct SQL query constructionAffected if The has_checkout_consent() method exists and uses direct string concatenation with the checkout_uuid parameter instead of $wpdb->prepare()
-
Identify exposure vectorDetermine if WooCommerce checkout consent feature is enabled or if any frontend/form component passes the checkout_uuid to the plugin. Check plugin settings for checkout integration optionsAffected if WooCommerce is active and the plugin's checkout consent functionality is accessible to unauthenticated users
Your environment is affected if Creative Mail plugin version is below 1.6.10 and the has_checkout_consent() method with the vulnerable checkout_uuid parameter is accessible on your site.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade to version 1.7.0 or later. If unable to upgrade immediately, consider disabling the plugin or implementing a web application firewall (WAF) rule to block SQL injection attempts targeting the checkout_uuid parameter.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3985 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-3985 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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