dbcve.org
Newsletter\, Smtp\, Email Marketing And SubscribeWordPress extension · Sendinblue

CVE-2024-43287

HIGH · 8.8 CVSS v3.1 Published 2024-08-26
Fix available
A fix is available. Upgrade to 3.1.83 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 Brevo Newsletter, SMTP, Email marketing and Subscribe forms by Sendinblue.This issue affects Newsletter, SMTP, Email marketing and Subscribe forms by Sendinblue: from n/a through 3.1.82.

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 Brevo (Sendinblue) WordPress plugin allows attackers to induce authenticated users to perform unintended state-changing actions. The lack of proper anti-CSRF token validation on form submissions or AJAX endpoints enables attackers to craft malicious requests that execute with the victim's privileges.

MitigationImplement anti-CSRF tokens (nonces) on all state-changing operations (form submissions, settings changes, list management) and validate these tokens on the server side before processing requests. Update to the patched version of the plugin when released.

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
Newsletter\, Smtp\, Email Marketing And SubscribeWordPress extension
Affected:< 3.1.83

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 Brevo plugin is installed
    Check the WordPress plugins directory for the Sendinblue plugin folder, typically at wp-content/plugins/sendinblue-manager/ or look for 'brevo' in wp-content/plugins/
    Affected if The plugin folder exists in the WordPress installation
  2. Identify installed plugin version
    Read the main plugin file header (e.g., sendinblue-manager.php) and locate the 'Version' comment, or check the WordPress plugins admin page for the installed version number
    Affected if The version number is lower than 3.1.83 (e.g., 3.1.82, 3.1.80, etc.)
  3. Confirm plugin is active
    Check the WordPress database wp_options table for active_plugins option, or verify via the WordPress admin plugins page that the Sendinblue/Brevo plugin is currently activated
    Affected if The plugin is active and running a version below 3.1.83
  4. Identify state-changing operations in use
    Review if the site uses any Brevo features that perform state changes: subscription form submissions, newsletter list management, email sending functions, or AJAX endpoints exposed by the plugin
    Affected if Any Brevo subscription forms, email marketing features, or list management tools are in use on the site

The environment is affected if the Brevo (Sendinblue) WordPress plugin is installed, active, and running version 3.1.82 or lower.

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.1.83 or later
Fixed in 3.1.83
Interim mitigation

Implement anti-CSRF tokens (nonces) on all state-changing operations (form submissions, settings changes, list management) and validate these tokens on the server side before processing requests. Update to the patched version of the plugin when released.

Recommended fix High confidence

3.1.83

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Brevo (formerly Sendinblue) Newsletter, SMTP, Email marketing plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to version 3.1.83 or later
  5. 5. Alternatively, download version 3.1.83 from the WordPress plugin repository or the vendor
  6. 6. Deactivate and delete the current version, then upload and install version 3.1.83
  7. 7. After upgrade, verify the plugin version shows 3.1.83 or higher

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

Fix this in Newsletter\, Smtp\, Email Marketing And Subscribe Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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