dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-67945

CRITICAL · 9.3 CVSS v3.1 Published 2026-01-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in MailerLite MailerLite – WooCommerce integration woo-mailerlite allows SQL Injection.This issue affects MailerLite – WooCommerce integration: from n/a through <= 3.1.2.

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

SQL injection vulnerability in the MailerLite WooCommerce integration plugin (woo-mailerlite) allows attackers to inject malicious SQL commands through unsanitized input in database queries. The vulnerability stems from improper neutralization of special elements in SQL commands, potentially enabling unauthorized database access, data exfiltration, or data manipulation.

MitigationUpdate the MailerLite WooCommerce integration plugin to the latest patched version once released by the vendor. Until a patch is available, consider disabling the plugin or implementing web application firewall rules to block SQL injection attack patterns.

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
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/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. Locate the MailerLite WooCommerce integration plugin
    Access WordPress admin panel, go to Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'woo-mailerlite' or similar MailerLite-related plugin folders
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Verify the plugin version
    In WordPress admin, click on the plugin to view its details and version number, or open the main plugin PHP file (e.g., woo-mailerlite.php) and look for the 'Version:' header in the plugin comments
    Affected if Version is present and needs comparison against the vendor's patched version once released
  3. Confirm WooCommerce integration is active
    Check WooCommerce > Settings > Emails or similar integration settings to see if MailerLite sync features (such as subscriber sync, order tracking) are configured and enabled
    Affected if MailerLite integration settings are configured and the plugin is actively syncing data with MailerLite services
  4. Inspect database query execution paths
    If you have access, review the plugin's PHP files for direct SQL queries (using $wpdb->prepare, $wpdb->query, or raw queries) that process user-supplied input from forms, API calls, or WooCommerce order/customer data
    Affected if The plugin executes SQL queries that incorporate unsanitized input from customer data, order fields, or form submissions

Your environment is affected if the MailerLite WooCommerce integration plugin is installed, active, and running an unpatched version that processes SQL queries with unsanitized user or order data input.

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 MailerLite WooCommerce integration plugin to the latest patched version once released by the vendor. Until a patch is available, consider disabling the plugin or implementing web application firewall rules to block SQL injection attack patterns.

Recommended fix Moderate confidence

Latest version available from WordPress plugin repository (version > 3.1.2)

  1. Check the current version of the MailerLite – WooCommerce integration plugin installed in WordPress/WooCommerce
  2. Navigate to Plugins > WooCommerce integration settings to confirm the installed version
  3. Attempt to update the plugin to the latest available version via WordPress admin dashboard (Plugins > Add New > Upload or WordPress repository)
  4. If automatic update is unavailable, manually download the latest version from the official WordPress plugin repository or MailerLite's official sources
  5. Backup the WordPress database and files before performing the update
  6. Deactivate and delete the old plugin, then install and activate the new version
  7. Verify the plugin functions correctly with WooCommerce after update
  8. Check MailerLite's official release notes or PatchStack for confirmed fixed version number
Caveat Review plugin changelog for any WooCommerce version requirement changes or settings that may need reconfiguration after upgrade

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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