dbcve.org
Wordpress Meta Data And Taxonomies FilterWordPress extension · Pluginus

CVE-2024-8624

CRITICAL · 9.9 CVSS v3.1 Published 2024-09-24
Fix available
A fix is available. Upgrade to 1.3.3.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available

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 MDTF – Meta Data and Taxonomies Filter plugin for WordPress is vulnerable to SQL Injection via the 'meta_key' attribute of the 'mdf_select_title' shortcode in all versions up to, and including, 1.3.3.3 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Contributor-level access and above, 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 MDTF WordPress plugin is vulnerable to SQL injection via the 'meta_key' attribute in the 'mdf_select_title' shortcode. The plugin fails to properly escape user input and lacks prepared statements, allowing authenticated users with Contributor-level access to inject malicious SQL queries and extract sensitive database information.

MitigationUpdate the MDTF plugin to a version beyond 1.3.3.3 that addresses this SQL injection vulnerability. If no patched version is available, disable the plugin immediately.

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
Wordpress Meta Data And Taxonomies FilterWordPress extension
Affected:< 1.3.3.4

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

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 MDTF plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'MDTF - Meta Data and Taxonomies Filter' or check the plugin files in /wp-content/plugins/mdtf/ for a version file
    Affected if The plugin is installed and active
  2. Check installed plugin version
    View the plugin header in the main plugin file (usually mdft.php) or look at the plugin details in the WordPress plugins list
    Affected if The version is 1.3.3.3 or lower (anything below 1.3.3.4)
  3. Detect use of vulnerable shortcode
    Search posts, pages, and custom post types for the 'mdf_select_title' shortcode, or search the database in wp_posts for '[mdf_select_title'
    Affected if The mdf_select_title shortcode is present in any published content
  4. Review user roles with elevated access
    In WordPress admin, go to Users and check which accounts have Contributor, Author, Editor, or Administrator roles
    Affected if There are users with Contributor-level access or higher who could exploit this vulnerability

You are affected if the MDTF plugin version is 1.3.3.3 or lower AND the mdf_select_title shortcode is in use AND users with Contributor or higher access exist on the site.

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.3.3.4 or later
Fixed in 1.3.3.4
Vendor patch plugins.trac.wordpress.org →
Interim mitigation

Update the MDTF plugin to a version beyond 1.3.3.3 that addresses this SQL injection vulnerability. If no patched version is available, disable the plugin immediately.

Recommended fix High confidence

1.3.3.4

  1. 1. Backup your WordPress site (database and files) before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
  3. 3. Find the 'MDTF – Meta Data and Taxonomies Filter' plugin in the list.
  4. 4. If an update is available, click 'Update Now' to upgrade to version 1.3.3.4.
  5. 5. Alternatively, you can manually upload the fixed plugin version from the WordPress plugin repository.
  6. 6. After updating, verify the plugin is running version 1.3.3.4 or higher in the plugins list.

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

Fix this in Wordpress Meta Data And Taxonomies Filter Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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