CVE-2026-109935 Otter Blocks < 3.2.8 - Unauthenticated Restricted Block Content Disclosure via REST API
Medium 5.3
Published
Updated
Check this codebase for CVE-2026-109935 and fix it if it is affected.
What it is: CVE-2026-109935 is a medium-severity vulnerability in Unknown Otter Blocks, published on 23 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-109935 in the wild and no public exploit code.
Affected product: Unknown Otter Blocks. 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-109935/ (Markdown: https://insights.sbomify.com/CVE-2026-109935/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-109935?
CVE-2026-109935 is a medium-severity vulnerability in Unknown Otter Blocks, published on 23 Oct 2026.
Official description
The Otter Blocks WordPress plugin before 3.2.8 does not enforce its block visibility conditions when a published post is rendered through the WordPress REST API, allowing unauthenticated users to read block content that the site owner restricted to specific roles, logged-in users, the post author, categories or tags, or (on the Pro tier) Stripe purchasers.
Weakness: CWE-200
Which versions are affected by CVE-2026-109935?
How do I fix CVE-2026-109935?
No fix has been published for CVE-2026-109935 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-109935 being exploited?
There is no known exploitation of CVE-2026-109935 in the wild and no public exploit code.
Sources
Also known as GHSA-3jfj-x8x5-pch2.