CVE-2026-102002

Otter Blocks <= 3.2.6 - Authenticated (Subscriber+) Sensitive Information Exposure in Form Submissions Dashboard Widget

2026-10-01 19:21
Jakub Herman

Strategic Overview

Status
Patched in 3.2.7
Affected Plugin
Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE
Affected Version
<= 3.2.6
CVSS
3.1Low
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2026-102002
View all Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE vulnerabilities

At a glance

CVE-2026-102002 is a low-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Otter Blocks WordPress plugin, affecting versions <= 3.2.6. It carries a CVSS score of 3.1 (reachable over the network). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.2.7; sites on affected versions should update now. Disclosed October 2026, reported by Jakub Herman.

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.2.6 via the 'otter_form_widget_filter' parameter. This makes it possible for authenticated attackers, with subscriber-level access and above, to extract the email addresses of the five most recent form submitters, their submission dates, and the site's total form submission count. The widget is registered whenever the themeisle_blocks_form_emails option is non-empty — the normal state after any Form block has been saved — meaning the exposure is active on any standard site using the plugin's form feature.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user.

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

Otter Blocks <= 3.2.6 carries this weakness at otter_form_widget_filter, and reaching it 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 the fix is 3.2.7: builds <= 3.2.6 are affected, anything from 3.2.7 onward is not.

Remediation

Update to version 3.2.7, or a newer patched version

How does WordSec protect against this?

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

  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-102002https://www.wordfence.com/threat-intel/vulnerabilities/id/6cf22af6-3e25-43ae-b10d-f343720e722ahttps://nvd.nist.gov/vuln/detail/CVE-2026-102002

Related records

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