CVE-2026-10823

YMC Smart Filter <= 3.11.2 - Unauthenticated Private/Draft Post Disclosure

2026-06-05 00:00
Ahmed Hashim Ismael

Strategic Overview

Status
Patched in 3.11.3
Affected Plugin
YMC Filter
Affected Version
<= 3.11.2
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2026-10823
View all YMC Filter vulnerabilities

At a glance

CVE-2026-10823 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the YMC Filter WordPress plugin, affecting versions <= 3.11.2. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.11.3; sites on affected versions should update now. Disclosed June 2026, reported by Ahmed Hashim Ismael.

Vulnerability Overview

The YMC Smart Filter plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 3.11.2. This is due to missing authentication and capability check before allowing non-public post statuses in the post_status parameter passed to the frontend posts REST API endpoint. This makes it possible for unauthenticated attackers to view private and draft posts by supplying non-public post statuses in the post_status parameter of the frontend posts REST API endpoint.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in YMC Filter <= 3.11.2 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For YMC Filter the fix is 3.11.3: builds <= 3.11.2 are affected, anything from 3.11.3 onward is not.

Remediation

Update to version 3.11.3, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: YMC Filter 3.11.3 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-10823https://www.wordfence.com/threat-intel/vulnerabilities/id/1753ce91-762e-4fb7-a164-ee5bc9dcd323https://nvd.nist.gov/vuln/detail/CVE-2026-10823

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C