Brevo Plugin up to 3.3.0 on WordPress REST API Endpoint mailin_disconnect ID authorization

Summaryinfo

A vulnerability, which was classified as critical, has been found in Brevo Plugin up to 3.3.0 on WordPress. This affects an unknown function of the file /wp-json/mailin/v1/mailin_disconnect of the component REST API Endpoint. Performing a manipulation of the argument ID results in authorization. This vulnerability is identified as CVE-2025-14799. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as critical, was found in Brevo Plugin up to 3.3.0 on WordPress. This affects an unknown functionality of the file /wp-json/mailin/v1/mailin_disconnect of the component REST API Endpoint. The manipulation of the argument id with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

It is possible to read the advisory at wordfence.com. This vulnerability is uniquely identified as CVE-2025-14799. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/18/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

• WordPress Plugin

Name

• Brevo Plugin

Version

• 3.0
• 3.1
• 3.2
• 3.3.0

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion