CVE-2024-35682

Otter Blocks PRO – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE <= 2.6.11 - Authenticated (Subscriber+) Information Exposure

2024-06-06 00:00
Dave Jong

Strategic Overview

Status
Patched in 2.6.12
Affected Version
<= 2.6.11
CVSS
4.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2024-35682
View all Otter Blocks PRO – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE vulnerabilities

At a glance

CVE-2024-35682 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Otter Blocks PRO WordPress plugin, affecting versions <= 2.6.11. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.6.12; sites on affected versions should update now. Disclosed June 2024, reported by Dave Jong.

Vulnerability Overview

The Otter Blocks PRO – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.6.11. This makes it possible for authenticated attackers, with Subscriber-level access and above, 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 interaction from a victim user.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in Otter Blocks PRO <= 2.6.11 takes an account at Subscriber level or above. 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 PRO the fix is 2.6.12: builds <= 2.6.11 are affected, anything from 2.6.12 onward is not.

Remediation

Update to version 2.6.12, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Otter Blocks PRO 2.6.12 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C