# CVE-2026-10823: YMC Smart Filter < 3.11.3 - Unauthenticated Private/Draft Post Disclosure

> Unauthenticated attackers can access private and draft post content via an unauthorized REST API endpoint in the YMC Filter WordPress plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jun 2026
- **Updated:** 26 Jun 2026
- **Also known as:** GHSA-cxq8-qm2q-phgj

## What is CVE-2026-10823?

CVE-2026-10823 is a high-severity missing authorization vulnerability in Unknown YMC Filter, published on 26 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2026-10823?


## How do I fix CVE-2026-10823?

No fix has been published for CVE-2026-10823 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-10823 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10823 exists.

Public exploit code:

- YMC Filter WordPress - Unauthenticated Post Disclosure (nuclei): http/cves/2026/CVE-2026-10823.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10823 and fix it if it is affected.

What it is: CVE-2026-10823 is a high-severity missing authorization vulnerability in Unknown YMC Filter, published on 26 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10823 exists.

Affected product: Unknown YMC Filter. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-10823/ (Markdown: https://insights.sbomify.com/CVE-2026-10823/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10823
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10823
- OSV: https://osv.dev/vulnerability/CVE-2026-10823

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-10823/
Summaries are generated and may contain mistakes; the official description above is the record.