dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-30807

CRITICAL · 9.3 CVSS v3.1 Published 2025-04-01
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 Martin Nguyen Next-Cart Store to WooCommerce Migration nextcart-woocommerce-migration allows SQL Injection.This issue affects Next-Cart Store to WooCommerce Migration: from n/a through <= 3.9.4.

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 confidence

SQL injection vulnerability in the Next-Cart Store to WooCommerce Migration plugin allows attackers to inject malicious SQL commands via unsanitized user inputs. This can lead to unauthorized database access, data exfiltration, or potential site compromise.

MitigationUpdate to a patched version of the plugin as soon as available; if no patch exists, disable the plugin and consider alternative migration solutions until a fix is released.

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. Verify plugin installation
    Navigate to WordPress admin > Plugins and look for 'Next-Cart Store to WooCommerce Migration' in the installed plugins list, or check the plugin files in wp-content/plugins/ for a directory named similar to 'nextcart-wcm' or containing 'next-cart'
    Affected if the plugin is installed and active
  2. Identify installed version
    In WordPress admin > Plugins, click on the plugin to view its details and note the version number displayed, or open the main plugin PHP file and look for a 'Version' header in the plugin comment block
    Affected if the installed version matches a known vulnerable version range (version comparison required once CVE details specify ranges)
  3. Confirm plugin is active
    Check the Plugins page in WordPress admin - the plugin must be both installed AND active for the SQL injection to be exploitable
    Affected if the plugin status shows 'Active'
  4. Inspect user input handling
    Review plugin source code files in the plugin directory, specifically looking for SQL query execution functions (like $wpdb->prepare, mysql_query, mysqli_query) that accept raw user input from $_POST, $_GET, or $_REQUEST parameters without sanitization
    Affected if unsanitized user-supplied parameters are used directly in SQL queries
  5. Check for exposed admin interfaces
    Verify if the plugin exposes any frontend or admin AJAX endpoints, REST API routes, or forms that accept user input and interact with the database - these are the potential injection points
    Affected if the plugin has active endpoints accepting user input without proper parameterization

The environment is affected if the Next-Cart Store to WooCommerce Migration plugin is installed, active, runs a vulnerable version, and processes user input through unsanitized SQL queries.

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 to a patched version of the plugin as soon as available; if no patch exists, disable the plugin and consider alternative migration solutions until a fix is released.

Recommended fix Moderate confidence

Latest available version of Next-Cart Store to WooCommerce Migration (version 3.9.5 or later)

  1. Backup your WordPress database and files before making any changes
  2. Update the Next-Cart Store to WooCommerce Migration plugin to the latest available version
  3. After updating, verify the plugin is functioning correctly with your WooCommerce store
  4. Test that the migration functionality works as expected

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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