dbcve.org
SendgridWordPress extension · Smackcoders

CVE-2024-43965

CRITICAL · 9.8 CVSS v3.1 Published 2024-08-29
Fix available
A fix is available. Upgrade to after 1.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Smackcoders SendGrid for WordPress allows SQL Injection.This issue affects SendGrid for WordPress: from n/a through 1.4.

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

SQL injection vulnerability in Smackcoders SendGrid for WordPress plugin allows attackers to inject malicious SQL commands via unsanitized input in SQL queries. The critical CVSS 9.8 score indicates the flaw is remotely exploitable without authentication and can lead to complete database compromise.

MitigationUpgrade SendGrid for WordPress to the latest version to obtain the patched code. If no patch is available, identify and parameterize all SQL queries in the plugin to use prepared statements instead of string concatenation.

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
SendgridWordPress extension
Affected:<= 1.4

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 SendGrid plugin is installed
    Check the WordPress plugins directory at wp-content/plugins/ for the sendgrid or sendgrid-for-wordpress folder, or list installed plugins via wp-cli: wp plugin list --search='*sendgrid*'
    Affected if The SendGrid plugin folder exists in the WordPress plugins directory
  2. Check installed plugin version
    Read the main plugin file header in wp-content/plugins/sendgrid-for-wordpress/sendgrid.php (or similar path) to find the 'Version:' field, or run: grep -i 'Version:' wp-content/plugins/sendgrid-for-wordpress/*.php
    Affected if The version number returned is 1.4 or lower (e.g., 1.4, 1.3, 1.2, 1.1, 1.0)
  3. Identify SQL query files in the plugin
    Search for direct SQL queries: grep -rn '\$wpdb->' wp-content/plugins/sendgrid-for-wordpress/ | grep -v 'prepare\|prepare()'
    Affected if SQL queries using $wpdb->query, $wpdb->get_results, or $wpdb->get_var without $wpdb->prepare() are found
  4. Check for unsanitized input in database operations
    Review the SQL query files found in step 3 for parameters received from $_GET, $_POST, or $_REQUEST that are directly concatenated into queries without sanitization functions like sanitize_text_field or esc_sql
    Affected if User-supplied input from request parameters is directly interpolated into SQL queries without escaping or prepared statements
  5. Verify plugin admin/frontend endpoints are accessible
    Check if the plugin exposes any admin AJAX hooks or public-facing forms that accept user input: grep -rn 'add_action.*admin_post\|add_action.*wp_ajax\|do_action\|apply_filters' wp-content/plugins/sendgrid-for-wordpress/ | head -20
    Affected if The plugin has active endpoints that process user input and could trigger the vulnerable SQL code

Your environment is affected if the SendGrid for WordPress plugin is installed with version 1.4 or lower and contains direct SQL queries that accept unsanitized user input.

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.

From vendor data
Upgrade available Upgrade to a release after 1.4
Interim mitigation

Upgrade SendGrid for WordPress to the latest version to obtain the patched code. If no patch is available, identify and parameterize all SQL queries in the plugin to use prepared statements instead of string concatenation.

Fix this in Sendgrid Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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