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

CVE-2024-50450

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-28
Fix available
A fix is available. Upgrade to 1.3.3.5 or later.
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 Control of Generation of Code ('Code Injection') vulnerability in RealMag777 MDTF wp-meta-data-filter-and-taxonomy-filter allows Code Injection.This issue affects MDTF: from n/a through <= 1.3.3.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

A code injection vulnerability exists in the WordPress plugin MDTF (wp-meta-data-filter-and-taxonomy-filter) version 1.3.3.4 and below. The vulnerability allows attackers to inject malicious code due to improper control of code generation, likely through unsanitized user input being evaluated or executed server-side.

MitigationUpdate the MDTF plugin to the latest version immediately. If no patch is available, disable the plugin until a fix is released. Review recent access logs for signs of exploitation.

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.5

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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
    Navigate to WordPress Admin > Plugins > Installed Plugins and look for 'MDTF' or 'Meta Data And Taxonomies Filter'. Alternatively, check the plugin directory via file system at wp-content/plugins/ for folders containing 'meta-data-filter' or 'mdtf'.
    Affected if The plugin is present in the WordPress installation
  2. Determine installed plugin version
    In WordPress Admin > Plugins, find the MDTF plugin and read the version number displayed below the plugin name. If using file system, open the main plugin file (usually index.php or the plugin's main PHP file) and look for the 'Version' header in the plugin comment block.
    Affected if The version is 1.3.3.4 or lower, or if the version cannot be determined and the plugin is present
  3. Identify if frontend filter functionality is exposed
    Check if shortcodes or filter forms using the plugin are publicly accessible. Visit pages containing [mdf_filter] or similar MDTF shortcodes. The vulnerability involves unsanitized user input being evaluated, typically through filter parameters in the frontend.
    Affected if Public-facing filter forms exist and accept user input that could be processed server-side
  4. Review access logs for exploitation attempts
    Examine web server access logs (Apache error.log, Nginx access.log, or WordPress debug.log) for suspicious patterns such as encoded characters, eval(, base64_decode, or unusual query parameters containing 'mdf_' prefix or filter-related endpoints.
    Affected if Log entries show suspicious input patterns or known exploitation payloads targeting the plugin

You are affected if the MDTF plugin is installed with a version lower than 1.3.3.5 AND the plugin's filter functionality is active on your 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.5 or later
Fixed in 1.3.3.5
Interim mitigation

Update the MDTF plugin to the latest version immediately. If no patch is available, disable the plugin until a fix is released. Review recent access logs for signs of exploitation.

Recommended fix High confidence

1.3.3.5

  1. Backup your WordPress site before making any changes
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Locate 'Meta Data And Taxonomies Filter' (MDTF) plugin
  4. Click 'Update now' if an update is available, or manually download version 1.3.3.5 from the WordPress plugin repository and upload it
  5. After updating, verify the installed version shows 1.3.3.5 in the Plugins list
  6. Test the plugin functionality to ensure it works correctly after the update

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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,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 $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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