dbcve.org
Product FilterWordPress extension · Themify

CVE-2024-6027

HIGH · 7.5 CVSS v3.1 Published 2024-06-21
Fix available
A fix is available. Upgrade to 1.5.0 or later.
See remediation →
84/100
Remediation priority · High
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
The Themify – WooCommerce Product Filter plugin for WordPress is vulnerable to time-based SQL Injection via the ‘conditions’ parameter in all versions up to, and including, 1.4.9 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 Themify – WooCommerce Product Filter WordPress plugin is vulnerable to time-based SQL injection via the 'conditions' parameter in versions up to 1.4.9. The vulnerability stems from insufficient escaping of user-supplied input combined with a lack of prepared statements in the existing SQL query, allowing unauthenticated attackers to inject arbitrary SQL queries and extract sensitive data from the database.

MitigationUpdate the plugin to version 1.5.0 or later which contains the patch. If immediate updating is not feasible, disable the plugin or deploy a WAF rule to block SQL injection attempts targeting the 'conditions' parameter.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Product FilterWordPress extension
Affected:< 1.5.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Confirm plugin installation
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Themify - WooCommerce Product Filter' or check the plugin directory wp-content/plugins/ for a folder containing 'themify' in the name.
    Affected if The plugin is not found in the installation.
  2. Identify installed version
    In the WordPress Plugins page, find the Themify Product Filter entry and read the version number displayed beneath the plugin name. Alternatively, open the main plugin PHP file (usually themify-woocommerce-product-filter.php or similar in wp-content/plugins/) and locate the 'Version' header in the plugin comment block.
    Affected if The version displayed is below 1.5.0 (e.g., 1.4.9, 1.4.8, etc.).
  3. Verify plugin is active
    In WordPress admin > Plugins, confirm the Themify Product Filter plugin shows as 'Active'. An inactive plugin may reduce exposure but the vulnerable code still exists in the codebase.
    Affected if The plugin is currently active and version is below 1.5.0.

You are affected if the Themify - WooCommerce Product Filter plugin is installed, active, and the version is below 1.5.0.

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
Upgrade available Upgrade to 1.5.0 or later
Fixed in 1.5.0
Interim mitigation

Update the plugin to version 1.5.0 or later which contains the patch. If immediate updating is not feasible, disable the plugin or deploy a WAF rule to block SQL injection attempts targeting the 'conditions' parameter.

Recommended fix High confidence

1.5.0

  1. Backup your WordPress database and files before making any changes
  2. Update the Themify – WooCommerce Product Filter plugin to version 1.5.0 or later through WordPress admin > Plugins > All Plugins, or upload the updated plugin package
  3. Verify the update was successful by checking the plugin version in WordPress admin > Plugins
  4. Test that the product filtering functionality works correctly after the update
  5. Confirm the site functions normally with no errors

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

Fix this in Product Filter Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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