Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-108175 Overview
CVE-2026-108175 is a stored cross-site scripting (XSS) vulnerability in the PluginUs.Net MDTF (Meta Data Filter and Taxonomy Filter) WordPress plugin. The flaw affects all plugin versions up to and including 1.4.0. It stems from improper neutralization of input during web page generation, classified under [CWE-79]. Authenticated contributors can inject malicious scripts that execute in the browsers of site administrators and visitors. The vulnerability requires low privileges and user interaction, but it crosses a security scope boundary once stored content renders.
Critical Impact
Attackers with low-privileged WordPress accounts can store malicious JavaScript that executes against administrators and site visitors, enabling session theft, account takeover, and content manipulation.
Affected Products
- PluginUs.Net MDTF (Meta Data Filter and Taxonomy Filter)
- MDTF plugin versions through 1.4.0
- WordPress installations with the wp-meta-data-filter-and-taxonomy-filter plugin active
Discovery Timeline
- 2026-10-15 - CVE-2026-108175 published to NVD
- 2026-10-15 - Last updated in NVD database
Technical Details for CVE-2026-108175
Vulnerability Analysis
The MDTF plugin fails to sanitize user-supplied input before rendering it inside WordPress pages. The payload persists in the database and executes each time an affected page loads. Because the issue is stored rather than reflected, exploitation does not require social engineering of a specific target URL. The scope change in the CVSS vector reflects that injected scripts can affect users beyond the attacker's own session, including site administrators viewing plugin-controlled content.
Successful exploitation can lead to session hijacking, forced administrative actions through CSRF chaining, redirect-to-malware campaigns, and defacement of filter widgets exposed to visitors.
Root Cause
The root cause is missing or insufficient output encoding on parameters handled by the MDTF plugin. WordPress provides functions such as esc_html(), esc_attr(), and wp_kses() for context-aware escaping. The plugin's filter and taxonomy rendering paths do not consistently apply these functions, allowing HTML and JavaScript to pass through to the DOM. The CWE-79 classification confirms this as an input-neutralization failure during web page generation.
Attack Vector
Exploitation requires an authenticated user with at least contributor-level privileges. The attacker submits crafted input to a plugin field that stores and later re-renders the data without encoding. When an administrator or site visitor loads the affected page, the injected script runs under the site's origin. See the Patchstack WordPress XSS Vulnerability advisory for the full technical write-up.
Detection Methods for CVE-2026-108175
Indicators of Compromise
- Unexpected <script>, <iframe>, or onerror= content stored in WordPress wp_postmeta or plugin option tables
- Outbound requests from browsers viewing plugin pages to attacker-controlled domains
- Administrator sessions terminating unexpectedly or new administrator accounts appearing without authorized provisioning
- WordPress audit log entries showing content edits by low-privileged contributor accounts targeting MDTF filter fields
Detection Strategies
- Scan plugin-controlled database fields for HTML event handlers and script tags using WordPress CLI queries
- Deploy a web application firewall with XSS signature coverage for known MDTF parameter names
- Enable Content Security Policy (CSP) reporting to surface inline script execution attempts on affected pages
- Review HTTP POST requests to wp-admin/admin-ajax.php and plugin endpoints for payloads containing encoded JavaScript
Monitoring Recommendations
- Alert on new or modified posts and taxonomy terms created by contributor-tier accounts
- Track administrator browser requests for outbound connections to uncategorized domains following page loads
- Monitor WordPress plugin version inventory to confirm MDTF remains on a patched release
How to Mitigate CVE-2026-108175
Immediate Actions Required
- Update the MDTF plugin to a version newer than 1.4.0 once a patched release is published by PluginUs.Net
- Audit all contributor, author, and editor accounts and remove any that are inactive or unrecognized
- Inspect existing MDTF filter configurations and taxonomy entries for stored script payloads and remove malicious content
- Rotate administrator session cookies and credentials if exploitation is suspected
Patch Information
At the time of publication, the Patchstack advisory lists MDTF versions through 1.4.0 as vulnerable. Apply the vendor patch immediately once released. Subscribe to the plugin's changelog on the WordPress plugin repository for update notifications.
Workarounds
- Deactivate the MDTF plugin until a fixed version is available if the filtering functionality is non-essential
- Restrict contributor-tier user registration and require administrator approval for new accounts
- Deploy a WAF rule to block requests containing <script>, javascript:, and common XSS payload patterns targeting plugin endpoints
- Implement a strict Content Security Policy that disallows inline scripts and restricts script sources to trusted origins
# Example WordPress CLI command to deactivate the vulnerable plugin
wp plugin deactivate wp-meta-data-filter-and-taxonomy-filter
# Verify current plugin version
wp plugin get wp-meta-data-filter-and-taxonomy-filter --field=version
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

