Live › vulnerability › CVE-2026-109983
Go to dashboardVersions of the YMC Filter plugin up to and including 3.12.19 fail to sanitize the post_title parameter, so a logged-in author can store a script that runs in visitors' browsers. The autocomplete REST endpoint has a permission callback that always returns true, so any visitor can trigger the payload through the filter search box.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Sites running the YMC Filter plugin at version 3.12.19 or earlier are exposed, since the autocomplete endpoint is reachable by any visitor. Sites without the plugin installed are not affected. Authors who cannot create posts add little extra risk, but any site with untrusted authors should treat this as relevant.
No product ranges from the sources yet.
wp plugin get ymc-filter --field=version (plugin slug assumed; unknown if the sources do not confirm it)3.12.19 (the first fixed version is unknown from the sources)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The YMC Filter plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'post_title' parameter in all versions up to, and including, 3.12.19 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The autocomplete REST endpoint is registered with a permission callback that unconditionally returns true, meaning any site visitor — including unauthenticated users — can trigger the payload simply by typing in the YMC filter search box, while only Author-level access is required to store it.
This page as .md · .json · in your agent: get_signal("CVE-2026-109983")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.