CVE-2025-66128
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 · uneditedMissing Authorization vulnerability in Brevo Sendinblue for WooCommerce woocommerce-sendinblue-newsletter-subscription allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Sendinblue for WooCommerce: from n/a through <= 4.0.49.
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 confidenceMissing authorization vulnerability in Brevo Sendinblue for WooCommerce plugin allows unauthenticated or low-privilege users to access or modify newsletter subscription settings due to incorrectly configured access control on certain plugin functions or AJAX endpoints.
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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Check the installed version of Brevo Sendinblue for WooCommerce pluginIn WordPress admin, go to Plugins > Installed Plugins and find 'Brevo Sendinblue for WooCommerce' (or 'Sendinblue for WooCommerce') to view the current version number. Alternatively, read the main plugin file header in wp-content/plugins/woocommerce-sendinblue/ or similar path.Affected if The installed version is 4.0.49 or earlier (versions prior to the fix)
-
Identify if the plugin handles newsletter subscription AJAX endpointsCheck the plugin directory for AJAX action handlers by searching for 'add_action' calls with 'wp_ajax' or 'wp_ajax_nopriv' hooks related to subscription functions. Examine the capability checks in those handlers.Affected if The plugin registers AJAX endpoints without proper capability checks or nonce validation for subscription-related actions
-
Verify user role permissions on sensitive plugin functionsTest whether low-privilege users (e.g., Subscriber role) can access plugin functions meant for administrators. Check if subscription settings, list management, or newsletter configuration is accessible to non-admin users.Affected if Users with subscriber or lower privileges can modify newsletter subscription settings or access plugin configuration without proper authorization
-
Inspect plugin configuration for public-facing subscription formsExamine the WordPress site for frontend newsletter subscription forms or widgets provided by the plugin. Check if these forms submit to AJAX endpoints accessible to unauthenticated users.Affected if The plugin exposes subscription functionality accessible to unauthenticated visitors without capability verification
You are affected if the Brevo Sendinblue for WooCommerce plugin version is 4.0.49 or earlier and unauthenticated or low-privilege users can access or modify newsletter subscription settings through plugin AJAX endpoints.
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.
From vendor dataUpdate the Sendinblue for WooCommerce plugin to the latest version beyond 4.0.49, or implement proper capability checks and nonce validation on all sensitive plugin actions.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66128 — 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-2025-66128 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