Otter Blocks: REST bypass of block visibility restrictions
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. Other endpoint, parameter, role or implementation details not named in this export are not established by this record. Affected versions: before 3.2.8.
- Component
- Otter Blocks
- Plugin slug
otter-blocks- Affected
- < 3.2.8
- Safe version
3.2.8- Published
- Oct 23, 2026
This CVE was published Oct 23, 2026 and is one of 20 known issues for this plugin.
Update, patch or deactivate.
The authoritative export identifies 3.2.8 as fixed. Update to the applicable fixed release or a later supported release. Enforce server-side caller, object and operation permissions at the disclosed trust boundary; do not treat knowledge of identifiers or a nonce as authorization.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical 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.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N