dbcve.org
Type ConfusionWeakness · CWE-843

CVE-2025-14799

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
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.

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 · high confidence

The Brevo WordPress plugin uses loose comparison (==) instead of strict comparison (===) when validating the installation ID in the `/wp-json/mailin/v1/mailin_disconnect` REST API endpoint. This allows unauthenticated attackers to bypass authorization by sending a boolean `true` value for the `id` parameter, exploiting PHP type juggling to pass the validation check.

MitigationUpdate the Brevo plugin to version 3.3.1 or later, which replaces loose comparison (==) with strict comparison (===) for ID validation in the affected endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

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 or use WP-CLI: `wp plugin list --status=active --format=csv` to list active plugins. Look for 'brevo' or 'mailin' in the output.
    Affected if The Brevo plugin (sometimes called 'Mailin' in older versions) appears in the active plugins list.
  2. Identify the Brevo plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Brevo. The version number is displayed below the plugin name. Alternatively, inspect the plugin header in wp-content/plugins/brevo/brevo.php or check via WP-CLI: `wp plugin get brevo --format=json`
    Affected if The installed version is less than 3.3.1 (vulnerable). Versions 3.3.1 and later contain the fix.
  3. Confirm REST API endpoint is accessible
    Send a GET request to `/wp-json/mailin/v1/mailin_disconnect` using curl or a browser. For example: `curl -s -o /dev/null -w "%{http_code}" https://your-site.com/wp-json/mailin/v1/mailin_disconnect`
    Affected if The endpoint responds (any HTTP status other than 404), indicating the vulnerable code path is present in the installation.
  4. Check for the type juggling behavior (optional confirmation)
    Send a request to the endpoint with `id=true` parameter, e.g., `curl -X POST https://your-site.com/wp-json/mailin/v1/mailin_disconnect -d "id=true"`. Compare the response to a request with a non-boolean string ID.
    Affected if Both requests produce the same response or both succeed, indicating loose comparison is in use (vulnerable). A strict comparison would reject the boolean `id=true` differently than string IDs.

You are affected if the Brevo plugin is installed with a version lower than 3.3.1 and the /wp-json/mailin/v1/mailin_disconnect REST API endpoint is accessible (returns a non-404 response).

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Brevo plugin to version 3.3.1 or later, which replaces loose comparison (==) with strict comparison (===) for ID validation in the affected endpoint.

Recommended fix Moderate confidence

Brevo plugin version 3.3.1 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Brevo (formerly Mailin/Sendinblue) plugin
  4. If an update is available, click 'Update Now' to install the latest version
  5. Alternatively, navigate to Dashboard > Updates and select the Brevo plugin to update
  6. After updating, verify the plugin version is higher than 3.3.0

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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