dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-47643

HIGH · 7.6 CVSS v3.1 Published 2025-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 Product Feed for WooCommerce allows SQL Injection. This issue affects ELEX Product Feed for WooCommerce: 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 · moderate confidence

SQL injection vulnerability in ELEX Product Feed for WooCommerce plugin allows attackers to inject malicious SQL commands through unsanitized input, potentially enabling unauthorized data access, modification, or disclosure from the WordPress database.

MitigationUpdate to a patched version when available; until then, restrict plugin access to trusted users only and implement WAF rules to filter SQL injection attempt 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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:H/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 'ELEX Product Feed for WooCommerce' in the installed plugins list
    Affected if the plugin is not installed
  2. Check plugin version
    In WordPress Admin > Plugins, click on the plugin to view its details and note the version number displayed
    Affected if the installed version is older than the patched version (compare against the latest version available in the WordPress plugin repository)
  3. Confirm plugin is active
    In WordPress Admin > Plugins, check if the plugin shows as 'Active' under its status
    Affected if the plugin is active and a vulnerable version is installed
  4. Inspect user accounts for unauthorized changes
    In WordPress Admin > Users, review all administrator accounts for any suspicious or unknown users that may have been created via SQL injection
    Affected if unexpected administrator accounts exist that were not created by legitimate administrators
  5. Review database for anomalous data
    Access phpMyAdmin or use WP-CLI to query the wp_options or wp_users tables for suspicious entries, particularly looking for unexpected admin users or modified option values
    Affected if unexpected records exist in the WordPress database that indicate compromise

A user is affected if the ELEX Product Feed for WooCommerce plugin is installed, active, and running a version prior to the patched release, or if unauthorized database changes are detected.

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 when available; until then, restrict plugin access to trusted users only and implement WAF rules to filter SQL injection attempt patterns.

Recommended fix Moderate confidence

Latest version newer than 3.1.2 (check WordPress plugin repository for current release)

  1. Check the WordPress plugin repository or ELEXtensions official website for the latest version of ELEX Product Feed for WooCommerce
  2. Navigate to Plugins > Installed Plugins in WordPress admin
  3. Locate ELEX Product Feed for WooCommerce in the plugins list
  4. If a newer version is available, click 'Update Now' to update the plugin
  5. After updating, verify the plugin is working correctly by generating a test product feed
  6. Check the plugin changelog to confirm the security fix for CVE-2025-47643 is included

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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