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

CVE-2024-29763

MEDIUM · 6.1 CVSS v3.1 Published 2024-03-27
Fix available
A fix is available. Upgrade to 1.3.3.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Reflected XSS.This issue affects WordPress Meta Data and Taxonomies Filter (MDTF): from n/a through 1.3.3.

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

Reflected XSS vulnerability in the WordPress Meta Data and Taxonomies Filter (MDTF) plugin allows attackers to inject malicious scripts through unsanitized user input that gets reflected in the web page output without proper encoding.

MitigationUpdate the MDTF plugin to the latest version after 1.3.3 to receive the security patch; if unavailable, locate and sanitize all user-supplied input before outputting to HTML using WordPress escaping functions.

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

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

CVSS:3.1/AV:N/AC:L/PR:N/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 is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Meta Data and Taxonomies Filter' or 'MDTF' in the list of active plugins
    Affected if The plugin appears in the installed plugins list
  2. Find installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find 'Meta Data and Taxonomies Filter', and click on the plugin name or 'View details' link to display the version number
    Affected if Version number displayed is below 1.3.3.1
  3. Check plugin file header for version
    If admin access is limited, access the plugin directory via FTP or file manager, navigate to /wp-content/plugins/meta-data-filter/, open the main PHP file (usually meta-data-filter.php or similar) and locate the 'Version' header in the plugin comment block
    Affected if Version header shows a version below 1.3.3.1
  4. Identify reflected input parameters
    Review the plugin's frontend output by testing search/filter forms that use MDTF. Submit common filter parameters (such as mdtf_search, _mdtf_paged, or custom meta field keys) with test values like <script>alert(1)</script> and observe if the value is reflected unescaped in the HTML response
    Affected if Test script tags appear literally in the page source without HTML encoding

You are affected if the Meta Data and Taxonomies Filter plugin is installed and the version is below 1.3.3.1, and your site exposes filter parameters that reflect user input without encoding.

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.1 or later
Fixed in 1.3.3.1
Interim mitigation

Update the MDTF plugin to the latest version after 1.3.3 to receive the security patch; if unavailable, locate and sanitize all user-supplied input before outputting to HTML using WordPress escaping functions.

Recommended fix High confidence

1.3.3.1

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find 'Meta Data and Taxonomies Filter' (MDTF) in the plugin list
  4. 4. If an update is available, click 'Update Now' to update to version 1.3.3.1
  5. 5. Alternatively, navigate to Plugins > Add New > Upload Plugin and upload version 1.3.3.1 of the plugin
  6. 6. After updating, verify the plugin version shows 1.3.3.1

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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