CVE-2026-130148 json
YMC Filter <= 3.14.1 - Authenticated (Subscriber+) Insufficient Authorization to Sensitive Information Exposure to 'post_status' Parameter
published 21h ago modified 21h ago also EUVD-2026-132015
- cvss
- 3.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 40%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2026-130148 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.46% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-21).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.1 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N |
| NVD | 3.1 | 3.1 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected products
- wssoffice21 YMC Filter
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/201804fe-b5a0-4162-8f2b-40413e96e5ff?source=cve
- plugins.trac.wordpress.org /browser/ymc-smart-filter/tags/3.14.1/ymc2/src/api/controllers/frontend/FG_REST_Frontend_Posts_Controller.php#
- plugins.trac.wordpress.org /browser/ymc-smart-filter/tags/3.14.1/ymc2/src/api/controllers/frontend/FG_REST_Frontend_Posts_Controller.php#
- plugins.trac.wordpress.org /browser/ymc-smart-filter/tags/3.14.1/ymc2/src/api/controllers/frontend/FG_REST_Frontend_Posts_Controller.php#
- plugins.trac.wordpress.org /browser/ymc-smart-filter/tags/3.14.1/ymc2/src/api/controllers/frontend/FG_REST_Frontend_Posts_Controller.php#
- plugins.trac.wordpress.org /browser/ymc-smart-filter/tags/3.14.1/ymc2/src/api/abstracts/FG_REST_Abstract_Controller.php#L66
- plugins.trac.wordpress.org /browser/ymc-smart-filter/tags/3.14.1/ymc2/src/functions/services/filter-options-service.php#L83
- plugins.trac.wordpress.org /log/ymc-smart-filter
- plugins.trac.wordpress.org /browser/ymc-smart-filter/tags/3.14.2/ymc2/src/api/controllers/frontend/FG_REST_Frontend_Posts_Controller.php
Sources
- CVE List CVE-2026-130148
- NVD CVE-2026-130148
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.