dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-47645

HIGH · 8.5 CVSS v3.1 Published 2025-07-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable 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 ELEXtensions ELEX WooCommerce Advanced Bulk Edit Products, Prices & Attributes elex-bulk-edit-products-prices-attributes-for-woocommerce-basic allows SQL Injection.This issue affects ELEX WooCommerce Advanced Bulk Edit Products, Prices & Attributes: from n/a through <= 1.4.9.

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 ELEX WooCommerce Advanced Bulk Edit Products plugin allows attackers to inject malicious SQL commands through unsanitized user inputs in the product/price bulk editing functionality. The flaw exists in versions up to and including 1.4.9, where user-supplied data in bulk edit operations is not properly neutralized before being incorporated into SQL queries.

MitigationUpdate to a patched version of the plugin once released by the vendor. If no patch is available, deactivate and remove the plugin until a fix is available, or implement input sanitization at the application layer as a temporary workaround.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm plugin installation
    Check your WordPress plugins directory for the 'elex-woocommerce-bulk-edit-products' or 'elex-bulk-edit' plugin folder, or look for 'ELEX WooCommerce Advanced Bulk Edit Products' in the WordPress admin Plugins page
    Affected if The plugin is installed and active on the WordPress site
  2. Identify installed version
    In WordPress admin, go to Plugins > Installed Plugins and look for the version number listed under the ELEX WooCommerce Advanced Bulk Edit Products plugin, or check the 'readme.txt' or 'elex-bulk-edit.php' file in the plugin folder for the 'Version' header
    Affected if The installed version is 1.4.9 or lower
  3. Verify WooCommerce is active
    Check that WooCommerce plugin is installed and active on the same WordPress site, as this is a WooCommerce-dependent plugin
    Affected if WooCommerce is active and the vulnerable plugin is installed
  4. Confirm bulk edit functionality is accessible
    Check if the bulk edit feature menu (usually under Products > Bulk Edit or a similar menu item added by the plugin) is visible and accessible in the WordPress admin dashboard
    Affected if The bulk edit functionality is accessible and the plugin version is 1.4.9 or below

A user is affected if the ELEX WooCommerce Advanced Bulk Edit Products plugin is installed with version 1.4.9 or lower and the bulk edit feature is accessible on a site running WooCommerce.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of the plugin once released by the vendor. If no patch is available, deactivate and remove the plugin until a fix is available, or implement input sanitization at the application layer as a temporary workaround.

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

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 locally
dbcve dependency scanner

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