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

CVE-2024-29906

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-27
Fix available
A fix is available. Upgrade to 1.3.3 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Input During Web Page Generation ('Cross-site Scripting') vulnerability in realmag777 WordPress Meta Data and Taxonomies Filter (MDTF) allows Stored XSS.This issue affects WordPress Meta Data and Taxonomies Filter (MDTF): from n/a through 1.3.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

A stored cross-site scripting (XSS) vulnerability exists in the WordPress Meta Data and Taxonomies Filter (MDTF) plugin versions through 1.3.2. The plugin fails to properly sanitize user-supplied input before reflecting it in web pages, allowing an attacker to inject malicious JavaScript code that executes when other users view the affected content.

MitigationUpdate the MDTF plugin to the latest patched version once available, or implement proper input validation and output escaping (using functions like esc_html(), esc_attr(), or wp_kses()) at all points where user input is displayed in the plugin.

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

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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. Verify MDTF plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find 'Meta Data and Taxonomies Filter' (or MDTF), and check the version number displayed under the plugin name. Alternatively, inspect the main plugin file (usually meta-data-filter.php or similar) and look for the 'Version' header comment.
    Affected if The version is 1.3.2 or lower (any version below 1.3.3)
  2. Confirm plugin is active
    Verify that the Meta Data and Taxonomies Filter plugin is currently activated in your WordPress site. Check the Plugins page status indicator.
    Affected if The plugin is activated and the version is below 1.3.3
  3. Identify filter functionality usage
    Review your site for any active filter widgets, shortcodes, or template usages of the MDTF plugin. Common indicators include filter forms on frontend pages, taxonomy filter widgets, or meta data filter shortcodes.
    Affected if The plugin's filter functionality is actively used on the site, allowing user-supplied input to be submitted
  4. Inspect user input reflection points
    Examine the plugin code for any instances where user-supplied GET/POST parameters, filter inputs, or taxonomy terms are displayed on pages without using sanitization functions such as esc_html(), esc_attr(), or wp_kses(). Focus on files handling filter submissions and output.
    Affected if User-supplied input from filter fields is reflected in page output without proper sanitization

If the installed MDTF plugin version is 1.3.2 or lower and the filter functionality is active on your site, you are affected by this stored XSS vulnerability.

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 or later
Fixed in 1.3.3
Interim mitigation

Update the MDTF plugin to the latest patched version once available, or implement proper input validation and output escaping (using functions like esc_html(), esc_attr(), or wp_kses()) at all points where user input is displayed in the plugin.

Recommended fix Moderate confidence

1.3.3

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Meta Data And Taxonomies Filter (MDTF)' plugin
  4. Check if the current version is below 1.3.3
  5. If vulnerable, click 'Update Now' to update to version 1.3.3
  6. Alternatively, navigate to Plugins > Add New > Upload Plugin and upload version 1.3.3 of the plugin
  7. After update, verify the new version is 1.3.3 or higher

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-29906 — 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-29906 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