Otter - Gutenberg Block <= 3.1.0 - Unauthenticated Sensitive Information Exposure
Strategic Overview
- Status
- Patched in 3.1.1
- Affected Version
<= 3.1.0- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2025-55715
At a glance
CVE-2025-55715 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Otter Blocks WordPress plugin, affecting versions <= 3.1.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.1.1; sites on affected versions should update now. Disclosed August 2025, reported by Abu Hurayra (HurayraIIT).
Vulnerability Overview
The Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.1.0. This makes it possible for unauthenticated attackers to extract sensitive user or configuration data.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in Otter Blocks <= 3.1.0 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Otter Blocks the fix is 3.1.1: builds <= 3.1.0 are affected, anything from 3.1.1 onward is not.
Remediation
Update to version 3.1.1, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Otter Blocks 3.1.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE
- 8.8CVE-2023-2288: Otter - Gutenberg Blocks <= 2.2.5 PHAR Deserialization
CVE-2023-2288 - 7.5CVE-2026-2892: Otter Blocks Improper Authorization
CVE-2026-2892 - 6.4CVE-2024-10367: Otter Blocks Stored XSS
CVE-2024-10367 - 6.4CVE-2024-3725: Otter Blocks Stored XSS
CVE-2024-3725 - 6.4CVE-2024-3343: Otter Blocks Stored XSS
CVE-2024-3343 - 6.4CVE-2024-3344: Otter Blocks Limited File Upload to Stored XSS
CVE-2024-3344 - 6.4CVE-2024-2841: Otter Blocks Stored XSS
CVE-2024-2841 - 6.4CVE-2024-2729: Otter Blocks <= 2.6.5 Stored Cross-Site Scripting
CVE-2024-2729
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C