dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-32455

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/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 MDTF wp-meta-data-filter-and-taxonomy-filter allows DOM-Based XSS.This issue affects MDTF: from n/a through <= 1.3.5.

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

DOM-based XSS vulnerability in the MDTF (wp-meta-data-filter-and-taxonomy-filter) WordPress plugin allows attackers to inject malicious JavaScript through unsanitized user input that gets executed in victims' browsers due to improper neutralization during web page generation.

MitigationUpdate to a patched version of the MDTF plugin when available, or implement proper output encoding and input validation in the plugin's JavaScript to neutralize malicious payloads.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L

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 'MDTF - wp-meta-data-filter-and-taxonomy-filter' or check the /wp-content/plugins/ directory for a folder containing 'meta-data-filter' in the name
    Affected if The plugin is installed and active
  2. Identify installed MDTF version
    In WordPress admin Plugins list, find MDTF and note the version number displayed, or inspect the main plugin file header in /wp-content/plugins/<mdtf-folder>/index.php for the 'Version' tag
    Affected if Version is at or below the last known vulnerable version (any unpatched version)
  3. Confirm frontend filter functionality is in use
    Check if any WordPress pages or posts contain the MDTF shortcode [mdtf_filter] or if the plugin's widget is actively used on the site
    Affected if The filter shortcode or widget is present and accessible to users
  4. Inspect page source for unsanitized parameters
    Load a page with MDTF filters active, view the browser page source, and look for GET/POST parameters (such as mdtf_[...] values) appearing directly in HTML without proper escaping
    Affected if User-supplied filter values appear unescaped in the rendered HTML

User is affected if the MDTF plugin is installed, active, and running an unpatched version with the filter functionality exposed on the 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of the MDTF plugin when available, or implement proper output encoding and input validation in the plugin's JavaScript to neutralize malicious payloads.

Have this fixed 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 help mitigating

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-2026-32455 — 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-2026-32455 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