# Otter Blocks <= 3.2.7 - Unauthenticated Block Visibility Conditions Bypass via REST API

- **ID:** WPSEC-2026-1357
- **Plugin:** Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE (`otter-blocks`), https://wordpress.org/plugins/otter-blocks/
- **Affected versions:** all versions before 3.2.8
- **Fixed in:** 3.2.8 (Update to 3.2.8 or later.)
- **Severity:** Medium 5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)
- **Weakness:** CWE-863
- **Usage among sites WPSec scans:** plugin Medium, affected versions Medium (as of 2026-10-21)
- **Attack surface analysis:** https://attacksurface.wpsec.com/plugin/otter-blocks
- **Fix released:** 2026-10-19
- **Published:** 2026-10-21
- **URL:** https://wpsec.com/vuln/WPSEC-2026-1357/

## Description

The Otter Blocks plugin for WordPress is vulnerable to a block visibility conditions bypass in all versions up to, and including, 3.2.7 due to block conditions being skipped for every REST API request. This makes it possible for unauthenticated attackers to retrieve, through REST responses that render block content, blocks that the site owner restricted with Otter block conditions (for example, blocks shown only to logged-in users).

## References

- https://wpsec.com/vuln/WPSEC-2026-1357/
- https://plugins.svn.wordpress.org/otter-blocks/tags/3.2.8/
- https://wordpress.org/plugins/otter-blocks/

Source: WPSec, https://wpsec.com/vuln/WPSEC-2026-1357/

License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Free to use, share and adapt, also commercially, if you credit WPSec and link to this advisory.