CVE-2024-43287

Newsletter, SMTP, Email marketing and Subscribe forms by Sendinblue <= 3.1.82 - Cross-Site Request Forgery

2024-08-16 00:00
Rafie Muhammad

Strategic Overview

Status
Patched in 3.1.83
Affected Plugin
Brevo – Email, SMS, Web Push, Chat, and more.
Affected Version
<= 3.1.82
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-43287
View all Brevo – Email, SMS, Web Push, Chat, and more. vulnerabilities

At a glance

CVE-2024-43287 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Brevo WordPress plugin, affecting versions <= 3.1.82. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.1.83; sites on affected versions should update now. Disclosed August 2024, reported by Rafie Muhammad.

Vulnerability Overview

The Newsletter, SMTP, Email marketing and Subscribe forms by Sendinblue plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.1.82. This is due to missing or incorrect nonce validation on the process_bulk_action() function. This makes it possible for unauthenticated attackers to perform bulk actions on forms via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Brevo <= 3.1.82 carries this weakness at process_bulk_action(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Brevo the fix is 3.1.83: builds <= 3.1.82 are affected, anything from 3.1.83 onward is not.

Remediation

Update to version 3.1.83, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Brevo: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Brevo 3.1.83 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-43287https://www.wordfence.com/threat-intel/vulnerabilities/id/11e31621-295a-4d34-8f11-65408bc75260https://nvd.nist.gov/vuln/detail/CVE-2024-43287

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C