CVE-2026-130148wssoffice21 YMC Filter information exposure
CVE-2026-130148 is a information exposure in wssoffice21 YMC Filter, rated low (3.1 on CVSS 3.1).
Why this priority: Low severity, with no exploitation signal.
Published · Updated · NVD status: Deferred
What it is
The software reveals data to someone who should not see it.
How it is reached
An attacker can exploit it over the network, with an ordinary user account, and nobody has to click anything. Success also depends on conditions the attacker does not fully control.
What an attacker gains
The direct impact is limited: partial access to data or a partial outage. In practice, this kind of flaw lets an attacker learn data or internals that help a follow-up attack.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- No fixed version is listed yet. Find every place wssoffice21 YMC Filter runs, watch the references for a fix, and plan a replacement if it is no longer supported.
- While there is no fix, review who holds accounts that can reach it.
Description from NVD
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.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- WordPress sites and their plugins. Plugins run inside the site with its database access, and many sites are public.
- Error responses, logs and debug endpoints. The flaw sits between internal data and whoever can read the response or log.
- APIs that over-share. The flaw sits between internal data and whoever can read the response or log.
Trust boundaries in play
- Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
- Between internal data and whoever can read the response or log. An attacker who crosses it can learn data or internals that help a follow-up attack.
Questions to answer about your own systems
- Where does wssoffice21 YMC Filter run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
14-day free trial
Understand how your systems connect.
See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.
Read more
Advisories
More reading
- 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/api/controllers/frontend/FG_REST_Frontend_Posts_Controller.php#L106
- plugins.trac.wordpress.org/browser/ymc-smart-filter/tags/3.14.1/ymc2/src/api/controllers/frontend/FG_REST_Frontend_Posts_Controller.php#L31
- plugins.trac.wordpress.org/browser/ymc-smart-filter/tags/3.14.1/ymc2/src/api/controllers/frontend/FG_REST_Frontend_Posts_Controller.php#L549
- plugins.trac.wordpress.org/browser/ymc-smart-filter/tags/3.14.1/ymc2/src/api/controllers/frontend/FG_REST_Frontend_Posts_Controller.php#L62
- 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/browser/ymc-smart-filter/tags/3.14.2/ymc2/src/api/controllers/frontend/FG_REST_Frontend_Posts_Controller.php
- plugins.trac.wordpress.org/log/ymc-smart-filter
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.