Radar sectionsDatabase
Check my site
WordPress plugin

Brevo — Email, SMS, Web Push, Chat, and more. <= 3.3.0 - Unauthenticated Authorization Bypass via Type Juggling

CVE-2025-14799Published · Updated

Action summary

Affected: ≤3.3.0Update to 3.3.1 or newer

All remediation steps
Severity
Medium6.5
CVSS
6.5
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:N Confidentiality
None
I:L Integrity
Low
A:L Availability
Low
Weakness
CWE-843 Access of Resource Using Incompatible Type
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

Brevo – Email, SMS, Web Push, Chat, and more. mailin

  1. Affected≤ 3.3.0
  2. Patched in3.3.1

Update to 3.3.1 or newer.

You are affected if you run ≤ 3.3.0. Version 3.3.1 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Brevo – Email, SMS, Web Push, Chat, and more..
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 3.3.1, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Brevo – Email, SMS, Web Push, Chat, and more. to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to ISMAILSHADOW.

The Brevo - Email, SMS, Web Push, Chat, and more. plugin for WordPress is vulnerable to authorization bypass due to type juggling in all versions up to, and including, 3.3.0. This is due to the use of loose comparison (==) instead of strict comparison (===) when validating the installation ID in the `/wp-json/mailin/v1/mailin_disconnect` REST API endpoint. This makes it possible for unauthenticated attackers to disconnect the Brevo integration, delete the API key, remove all subscription forms, and reset plugin settings by sending a boolean `true` value for the `id` parameter, which bypasses the authorization check through PHP type juggling.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Brevo – Email, SMS, Web Push, Chat, and more.

All 9
More vulnerabilities in Brevo – Email, SMS, Web Push, Chat, and more.
SeverityVulnerabilityCVEPublished
Medium4.3Cross-Site Request Forgery
≤3.1.87Update to 3.1.88
CVE-2024-8477
Medium4.3Cross-Site Request Forgery
≤3.1.82Update to 3.1.83
CVE-2024-43287
Medium6.1Reflected Cross-Site Scripting
≤3.1.77Update to 3.1.78
CVE-2024-35668
Medium6.1Reflected Cross-Site Scripting
≤3.1.77Update to 3.1.78
CVE-2026-15297
Medium6.1Reflected Cross-Site Scripting via 'lang'
≤3.1.60Update to 3.1.61
CVE-2023-2472

Timeline

  1. CVE published

    Severity medium, CVSS 6.5

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?