Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Unauthenticated network REST request (AV:N/AC:L/PR:N/UI:N) discloses non-public post content (C:H) with no integrity or availability impact (I:N/A:N).
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
5DescriptionCVE.org
The YMC Filter WordPress plugin before 3.11.3 does not properly authorize access to one of its REST API endpoints and does not validate a user-supplied query parameter, allowing unauthenticated attackers to retrieve the titles and content of private, draft, and other non-public posts.
Articles & Coverage 1
AnalysisAI
Information disclosure in the YMC Filter WordPress plugin before 3.11.3 lets unauthenticated remote attackers read the titles and content of private, draft, and other non-public posts by abusing a REST API endpoint that lacks proper authorization and fails to validate a user-supplied query parameter. WPScan reported the flaw, a public exploit exists, and a vendor patch is available; the CVSS 3.1 score is 7.5 reflecting high confidentiality impact with no integrity or availability effect.
Technical ContextAI
The affected component is the YMC Filter plugin for WordPress, which exposes one or more endpoints through the WordPress REST API. The root cause is a broken/missing authorization check (a Broken Access Control / missing function-level authorization class issue - no CWE was assigned in the input) combined with insufficient input validation of a user-supplied query parameter. By supplying that parameter to the unprotected REST route, an attacker can coerce the plugin into returning post objects that WordPress would normally restrict to authenticated, capability-bearing users (e.g. posts with status 'private', 'draft', 'pending', or other non-published states). The single CPE provided, cpe:2.3:a:unknown:ymc_filter:*:*:*:*:*:*:*:*, identifies the product but lists the vendor as 'unknown' and does not bound the version in the CPE itself.
RemediationAI
Vendor-released patch: upgrade the YMC Filter plugin to version 3.11.3 or later, which is the primary and recommended fix; consult the WPScan advisory at https://wpscan.com/vulnerability/b55ebf9e-a05d-4ae4-b653-da7db63e76d2/ for confirmation. If immediate patching is not possible, compensating controls include deactivating the YMC Filter plugin entirely (side effect: any filtering functionality it provides will stop working), or restricting access to the plugin's vulnerable REST API route at the web-server or WAF layer by blocking unauthenticated requests to the plugin's REST namespace under /wp-json/ (side effect: legitimate front-end features that call the endpoint anonymously may break). Avoid storing highly sensitive material in draft/private posts on exposed sites until patched, and review access logs for anomalous REST API queries.
More in Ymc Filter
View allSQL injection in the YMC Filter (YMC Smart Filter / Filter Grids) WordPress plugin lets remote attackers inject maliciou
Stored cross-site scripting in the YMC Filter WordPress plugin (all versions before 3.12.9) allows Author-role users to
Stored cross-site scripting in the YMC Filter WordPress plugin (versions 3.6.0 through 3.12.7) enables any Contributor-l
Same technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-39624
GHSA-cxq8-qm2q-phgj