Newsletter\, Smtp\, Email Marketing And SubscribeWordPress extension · Brevo
CVE-2024-35668
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 · uneditedImproper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Brevo Newsletter, SMTP, Email marketing and Subscribe forms by Sendinblue allows Reflected XSS.This issue affects Newsletter, SMTP, Email marketing and Subscribe forms by Sendinblue: from n/a through 3.1.77.
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 confidenceA reflected XSS vulnerability exists in Brevo (formerly Sendinblue) email marketing plugin versions through 3.1.77. The vulnerability allows attackers to inject malicious scripts through unsanitized input parameters that are reflected in web pages without proper output encoding.
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
< 3.1.78CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Confirm Brevo plugin installationAccess WordPress Admin and navigate to Plugins, or check the /wp-content/plugins/ directory on the server for the Brevo (formerly Sendinblue) email marketing pluginAffected if The Brevo email marketing plugin is installed on the WordPress site
-
Identify installed versionIn WordPress Admin > Plugins, click on the Brevo plugin to view version details, or open the main plugin PHP file and locate the 'Version' field in the plugin header commentAffected if Plugin version is 3.1.77 or any version lower than 3.1.78
-
Verify vulnerable parameter handling existsThe vulnerability involves unsanitized input parameters being reflected in web pages. Inspect plugin pages that accept user input (such as subscription forms, settings pages, or API endpoints) and check if input is reflected in output without proper encodingAffected if Plugin processes user input and reflects it in pages without output encoding, and version is below 3.1.78
Environment is affected if Brevo plugin version is 3.1.77 or earlier (any version prior to 3.1.78) and the plugin handles user input that gets reflected in pages.
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.
dbcve · scoped3.1.78
Upgrade to version 3.1.78 or later. Until then, implement output encoding on all user-supplied input displayed in pages and consider deploying a WAF rule to block XSS attack patterns in requests.
3.1.78 or later
- Backup your WordPress site before making any changes
- Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
- Find the Brevo (formerly Sendinblue) plugin
- Click 'Update now' if an update is available, or manually update to version 3.1.78 or later
- After updating, verify the plugin version shows 3.1.78 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
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35668 — 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-2024-35668 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