The YMC Filter plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.14.1 via the 'post_status' parameter
Source GCVE Database
Not known to be exploited · CVSS 3.1 Low.
Data as of 21 Nov 2026, 10:59 UTC
Thin evidence
One scorer or none| CNA (Wordfence) | CVSS 3.1 | 3.1 |
|---|
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| wssoffice21YMC Filter | Affected
| Fixed in– |
Description
The YMC Filter plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.14.1 via the 'post_status' parameter. This makes it possible for authenticated attackers, with subscriber-level access and above, to extract retrieve rendered grid HTML containing titles, excerpts, author names, dates, categories, tags, and thumbnails of private, draft, pending, and future posts they do not have permission to view. Exposure only occurs when an administrator has configured at least one non-publish status in the filter grid's Appearance → Post Status setting, as attacker-supplied statuses are intersected with this administrator-defined allowlist before being passed to WP_Query.
References
- nvd.nist.gov/vuln/detail/CVE-2026-130148 (opens in a new tab)
- plugins.trac.wordpress.org/browser/ymc-smart-filter/tags/3.14.1/ymc2/src/api/abstracts/FG_REST_Abstract_Controller.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/ymc-smart-filter/tags/3.14.1/ymc2/src/api/controllers/frontend/FG_REST_Frontend_Posts_Controller.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/ymc-smart-filter/tags/3.14.1/ymc2/src/api/controllers/frontend/FG_REST_Frontend_Posts_Controller.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/ymc-smart-filter/tags/3.14.1/ymc2/src/api/controllers/frontend/FG_REST_Frontend_Posts_Controller.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/ymc-smart-filter/tags/3.14.1/ymc2/src/api/controllers/frontend/FG_REST_Frontend_Posts_Controller.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/ymc-smart-filter/tags/3.14.1/ymc2/src/functions/services/filter-options-service.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/ymc-smart-filter/tags/3.14.2/ymc2/src/api/controllers/frontend/FG_REST_Frontend_Posts_Controller.php (opens in a new tab)
- plugins.trac.wordpress.org/log/ymc-smart-filter (opens in a new tab)
- wordfence.com/threat-intel/vulnerabilities/id/201804fe-b5a0-4162-8f2b-40413e96e5ff?source=cve (opens in a new tab)