Radar sectionsDatabase
Check my site
WordPress plugin

Meta Data Filter & Taxonomies Filter <= 1.2.7.2 — Cross-Site Request Forgery

CVE-2021-20781Published · Updated

Action summary

Affected: <2.2.8Update to 2.2.8 or newer

All remediation steps
Severity
High8.8
CVSS
8.8
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:R User interaction
Required
S:U Scope
Unchanged
C:H Confidentiality
High
I:H Integrity
High
A:H Availability
High
Weakness
CWE-352 CSRF
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

MDTF – Meta Data and Taxonomies Filter wp-meta-data-filter-and-taxonomy-filter

  1. Affected< 2.2.8
  2. Patched in2.2.8

Update to 2.2.8 or newer.

You are affected if you run < 2.2.8. Version 2.2.8 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under MDTF – Meta Data and Taxonomies Filter.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 2.2.8, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch MDTF – Meta Data and Taxonomies Filter to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Ryoma Nishioka.

The Meta Data Filter & Taxonomies Filter plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions versions prior to v.2.2.8. This is due to missing or incorrect nonce validation on the draw_settings_page() function. This makes it possible for unauthenticated attackers to inject malicious JavaScript via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in MDTF – Meta Data and Taxonomies Filter

All 25
More vulnerabilities in MDTF – Meta Data and Taxonomies Filter
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting via 'vars' Parameter
≤1.4.1Update to 1.4.2
CVE-2026-110776
Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting
≤1.4.0Update to 1.4.1
CVE-2026-108175
Critical9.8Unauthenticated Remote Code Execution
≤1.3.9Update to 1.4.0
CVE-2026-108151
High8.1Unauthenticated Local File Inclusion
≤1.3.8Update to 1.3.9
CVE-2026-54845
High7.5Unauthenticated SQL Injection
≤1.3.7Update to 1.3.8
CVE-2026-54843

Same weakness (CSRF)

All CSRF
Other CSRF vulnerabilities
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting via Comment User-Agent HeaderCVE-2026-120688
Critical9.8Unauthenticated Arbitrary File Upload via File Upload via Public Form SubmissionCVE-2026-125055
Critical9.8Unauthenticated PHP Object Injection to Remote Code Execution via 'form' ParameterCVE-2026-119077
Medium5.3Unauthenticated Sensitive Information Exposure in 'search' Parameter
Customer Reviews for WooCommerce≤5.127.0Update to 5.128.0
CVE-2026-121518

Timeline

  1. CVE published

    Severity high, CVSS 8.8

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?