---
id: "CVE-2026-109935"
kind: "vulnerability"
aliases: ["CVE-2026-109935"]
title: "Otter Blocks WordPress plugin: hidden block content readable through REST API"
severity: "medium"
cvss: null
epss: 0.00146
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["otter-blocks", "package", "self-hosted", "wordpress"]
not_affected_if: ["default-config", "no-visibility-conditions"]
published_at: "2026-10-23T06:17:05+00:00"
first_seen_at: "2026-10-23T21:57:32+00:00"
updated_at: "2026-10-25T05:00:20+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-109935", "first_seen_at": "2026-10-23T21:57:32+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-109935", "first_seen_at": "2026-10-24T07:15:51+00:00"}]
---

# Otter Blocks WordPress plugin: hidden block content readable through REST API

The Otter Blocks WordPress plugin before 3.2.8 does not apply its block visibility rules when a published post is rendered through the WordPress REST API. An unauthenticated visitor can read content the site owner hid from them, including content limited to specific roles, logged-in users, categories, tags, or Stripe purchasers on the Pro tier.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed Otter Blocks version in the WordPress admin plugins list or with `wp plugin get otter-blocks --field=version`
- Look for posts that use Otter Blocks visibility conditions and request them anonymously at `/wp-json/wp/v2/posts/<id>` to see if the restricted block content appears

## Fix

- Update Otter Blocks to `3.2.8` or later
- If you cannot update yet, move restricted content out of posts or disable the plugin's visibility conditions

## Timeline

- 2026-10-23T21:57:32+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-109935
- 2026-10-24T07:15:51+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-109935

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_