CVE-2026-10823
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe YMC Filter WordPress plugin before version 3.11.3 contains an insecure REST API endpoint that lacks proper authorization checks and fails to validate a user-supplied query parameter. This allows unauthenticated attackers to retrieve the titles and content of private, draft, and other non-public posts through the vulnerable endpoint.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm YMC Filter plugin is installedLog into WordPress admin and navigate to Plugins. Look for YMC Filter in the list of installed plugins.Affected if YMC Filter plugin is present in the WordPress installation
-
Check the installed version numberIn the Plugins list, click on YMC Filter to view its details. Note the version number displayed.Affected if Version is below 3.11.3 (for example, 3.11.2, 3.11.1, etc.)
-
Identify the REST API endpointUse a browser or curl to access the WordPress REST API schema at /wp-json/ and look for routes under the 'ymc' namespace (such as /wp-json/ymc/v1/...)Affected if An endpoint under the ymc namespace exists and responds to requests
-
Test for unauthenticated access to non-public postsSend a GET request to the YMC Filter REST API endpoint with typical query parameters (such as posts per page or taxonomy filters) without providing any authentication credentials. Examine the response for titles or content of private, draft, or non-public posts.Affected if The response contains titles or full content of private, draft, or password-protected posts without requiring authentication
You are affected if YMC Filter plugin version is below 3.11.3 AND the REST API endpoint is accessible to unauthenticated users and returns non-public post content.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the YMC Filter plugin to version 3.11.3 or later, which adds proper authorization verification and query parameter validation to the REST API endpoint.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10823 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-10823 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data