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

CVE-2024-34434

MEDIUM · 6.5 CVSS v3.1 Published 2024-05-17
Fix available
A fix is available. Upgrade to 1.3.3.3 or later.
See remediation →
74/100
Remediation priority · Elevated
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
Incorrect Authorization vulnerability in realmag777 WordPress Meta Data and Taxonomies Filter (MDTF) allows Code Inclusion, Functionality Misuse.This issue affects WordPress Meta Data and Taxonomies Filter (MDTF): from n/a through 1.3.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

An Incorrect Authorization vulnerability in the WordPress Meta Data and Taxonomies Filter (MDTF) plugin up to version 1.3.3.2 allows authenticated users to include arbitrary code or misuse plugin functionality due to insufficient authorization checks on certain endpoints or actions.

MitigationImplement proper authorization and capability checks on all sensitive plugin functions, particularly those involving code inclusion or functionality execution. Verify user roles and permissions before allowing access to potentially dangerous features.

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.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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Identify if MDTF plugin is installed
    Locate the plugin directory (commonly wp-content/plugins/mdtf-meta-data-and-taxonomies-filter or similar) and check for its main PHP file, or query the WordPress database wp_options table for the active_plugins entry
    Affected if The plugin directory or database entry exists and the plugin name contains 'Meta Data and Taxonomies Filter' or 'MDTF'
  2. Determine installed plugin version
    Open the plugin's main PHP file (typically index.php or the primary plugin file) and locate the version comment/constant at the top, or check the WordPress plugins admin page for the version number
    Affected if The version number found is lower than 1.3.3.3 (for example, 1.3.3.2, 1.3.3.1, or earlier)
  3. Verify plugin is active on the site
    Check the WordPress admin under Plugins > Installed Plugins to confirm the MDTF plugin is activated, or query the wp_options table for the active_plugins option containing the plugin's main file
    Affected if The plugin shows as Active in WordPress admin or its entry appears in the active_plugins option
  4. Confirm WordPress user accounts exist
    Check the wp_users table in the WordPress database or navigate to Users > All Users in the WordPress admin dashboard
    Affected if There is at least one user account registered on the WordPress site (since the vulnerability affects authenticated users)
  5. Identify if sensitive plugin endpoints are accessible
    Review the plugin's registered AJAX actions (wp_ajax_ hooks) and admin pages by examining the plugin code, or use a WordPress security scanner to enumerate available plugin endpoints
    Affected if The plugin exposes AJAX actions or admin pages that handle code inclusion or functionality execution without proper capability checks

A site is affected if it has the MDTF plugin installed with a version below 1.3.3.3, the plugin is active, and the site has at least one registered user account that could potentially access the insufficiently protected endpoints.

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.3 or later
Fixed in 1.3.3.3
Interim mitigation

Implement proper authorization and capability checks on all sensitive plugin functions, particularly those involving code inclusion or functionality execution. Verify user roles and permissions before allowing access to potentially dangerous features.

Recommended fix Moderate confidence

1.3.3.3

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Meta Data and Taxonomies Filter' (MDTF) plugin
  4. Check the current version installed
  5. If the version is below 1.3.3.3, click 'Update Now' to upgrade to version 1.3.3.3
  6. Alternatively, download version 1.3.3.3 from the WordPress Plugin Repository and upload it manually via Plugins > Add New > Upload Plugin
  7. After update, verify the version is 1.3.3.3 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
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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