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

CVE-2024-32818

HIGH · 8.8 CVSS v3.1 Published 2024-06-09
Fix available
A fix is available. Upgrade to 1.3.3.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Missing Authorization vulnerability in realmag777 WordPress Meta Data and Taxonomies Filter (MDTF).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 · high confidence

The WordPress Meta Data and Taxonomies Filter (MDTF) plugin lacks proper authorization checks, allowing authenticated attackers with subscriber-level or higher privileges to access administrative functions or modify plugin settings they should not have access to.

MitigationUpdate the plugin to the latest version which includes proper authorization checks; if no patch is available, disable the plugin or restrict access to administrative functions via server-level controls.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm MDTF plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Meta Data and Taxonomies Filter' or 'MDTF' in the installed plugins list
    Affected if The plugin appears in the plugins list and is activated
  2. Check installed plugin version
    In WordPress admin > Plugins, click on the MDTF plugin to view its details, or check the plugin file header in wp-content/plugins/mdtf-plugin-version/.../index.php for the 'Version' comment
    Affected if The version number is lower than 1.3.3.1 (for example, 1.3.3.0, 1.3.2.x, etc.)
  3. Verify user roles present
    In WordPress admin > Users, review the list of registered users and their assigned roles. Look for accounts with 'Subscriber' role or any role above it (Contributor, Author, Editor, Administrator)
    Affected if There are user accounts with subscriber-level or higher privileges, especially if any are untrusted or unused
  4. Check if plugin settings are accessible to low-privilege users
    Attempt to access the MDTF plugin settings page (usually under 'MDTF' or 'Filters' in the admin menu) using a test account that has only Subscriber role. Observe if settings pages load without being redirected or denied
    Affected if A subscriber-level user can view or modify plugin settings without being blocked

You are affected if the MDTF plugin is installed with a version below 1.3.3.1 and your site has any subscriber-level or higher user accounts, since the missing authorization allows these users to access admin functions.

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 plugin to the latest version which includes proper authorization checks; if no patch is available, disable the plugin or restrict access to administrative functions via server-level controls.

Recommended fix High confidence

Wordpress Meta Data And Taxonomies Filter version 1.3.3.1

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Meta Data and Taxonomies Filter (MDTF)' plugin
  4. Check if the current version is below 1.3.3.1
  5. If vulnerable, click 'Update now' when an update is available, or manually download version 1.3.3.1 from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin version shows 1.3.3.1 or higher
  7. Test the plugin functionality to ensure the update did not break expected features

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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