dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-15297

MEDIUM · 6.1 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 6 weeks old

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 Newsletter, SMTP, Email marketing and Subscribe forms by Brevo (formely Sendinblue) plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the page parameter in all versions up to, and including, 3.1.77 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

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 (Sendinblue) WordPress plugin versions up to 3.1.77 are vulnerable to reflected XSS via the page parameter due to insufficient input sanitization and output escaping. An unauthenticated attacker can inject arbitrary JavaScript through a malicious URL that tricks users into clicking it, leading to session hijacking or other client-side attacks.

MitigationUpgrade the Brevo plugin to version 3.1.78 or later, which includes proper sanitization of the page parameter and output escaping. Until patched, avoid clicking untrusted links pointing to the WordPress admin area.

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

Work through these to decide whether this CVE applies to you.

  1. Verify Brevo plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Brevo' or 'Sendinblue' plugin. Alternatively, check the /wp-content/plugins/ directory for a folder named 'mailin' or 'brevo'.
    Affected if The Brevo plugin is installed and active
  2. Check installed Brevo plugin version
    In WordPress admin > Plugins, find Brevo and note the version number displayed under the plugin name. Alternatively, check the main plugin file header in /wp-content/plugins/mailin/ or /wp-content/plugins/brevo/ for the 'Version' tag.
    Affected if The version is 3.1.77 or lower
  3. Verify vulnerable parameter handling exists
    Inspect the main Brevo plugin PHP files (particularly admin/class-mailin-admin.php or similar) for usage of the 'page' parameter from $_GET or $_REQUEST without sanitization via sanitize_text_field, esc_html, or similar escaping functions.
    Affected if The 'page' parameter is used in admin URLs without proper sanitization and output escaping
  4. Review access logs for exploitation attempts
    Check Apache/Nginx access logs in /var/log/ for requests to /wp-admin/admin.php with a 'page' parameter containing suspicious characters like <script>, javascript:, or other XSS vectors.
    Affected if Logs show requests with malicious XSS payloads in the 'page' parameter

You are affected if the Brevo plugin version is 3.1.77 or lower and the vulnerable parameter handling code is present in your installation.

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

Upgrade the Brevo plugin to version 3.1.78 or later, which includes proper sanitization of the page parameter and output escaping. Until patched, avoid clicking untrusted links pointing to the WordPress admin area.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (version 3.1.78 or higher)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Newsletter, SMTP, Email marketing and Subscribe forms by Brevo' plugin
  4. If an update is available, click 'Update Now' to update to the latest version
  5. Alternatively, navigate to Plugins > Add New > Upload and upload the latest version from the WordPress plugin repository
  6. Verify the updated version is above 3.1.77

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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