WordPress plugin · Updated daily · Source: Wordfence Intelligence

Otter Blocks vulnerabilities: affected versions and fixes

Otter Blocks has 300,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

Otter Blocks at a glance

  • 20 publicly disclosed vulnerabilities, 3 of them rated High or Critical. The most recent was disclosed on Oct 23, 2026.
  • Ranked #178 by popularity on WordPress.org (300,000+ active installs).
  • The latest version is 3.2.11 (released Nov 13, 2026). The most recent security fix shipped in 3.2.8.
  • Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your Otter Blocks version

Enter the Otter Blocks version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “Otter Blocks”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Otter Blocks”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (3.2.11). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known Otter Blocks vulnerabilities

  • Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE < 3.2.8 - Unauthenticated Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2026-109936

    Affected versions: < 3.2.8

    Fixed in: 3.2.8

    Severity: High 7.2 · Disclosed Oct 23, 2026

  • Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE < 3.2.8 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2026-109933

    Affected versions: < 3.2.8

    Fixed in: 3.2.8

    Severity: Medium 6.4 · Disclosed Oct 23, 2026

  • Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE < 3.2.8 - Missing Authorization

    Missing authorization · CVE-2026-109935

    Affected versions: < 3.2.8

    Fixed in: 3.2.8

    Severity: Medium 5.3 · Disclosed Oct 23, 2026

  • Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE 3.1.1 - 3.2.7 - Missing Authorization

    Missing authorization · CVE-2026-109934

    Affected versions: ≥ 3.1.1, ≤ 3.2.7

    Fixed in: 3.2.8

    Severity: Medium 5.3 · Disclosed Oct 23, 2026

  • Otter Blocks <= 3.2.2 - Unauthenticated Open Redirect

    Open redirect · CVE-2026-109937

    Affected versions: ≤ 3.2.2

    Fixed in: 3.2.3

    Severity: Medium 4.7 · Disclosed Oct 16, 2026

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

    Information disclosure · CVE-2026-102002

    Affected versions: ≤ 3.2.6

    Fixed in: 3.2.7

    Severity: Low 3.1 · Disclosed Oct 1, 2026

  • Otter Blocks <= 3.1.7 - Missing Authorization to Unauthenticated Purchase Verification Bypass

    Missing authorization · CVE-2026-4945

    Affected versions: ≤ 3.1.7

    Fixed in: 3.1.8

    Severity: Medium 5.3 · Disclosed Sep 6, 2026

  • Otter Blocks <= 3.1.4 - Improper Authorization to Unauthenticated Purchase Verification Bypass via Forged Cookie

    Missing authorization · CVE-2026-2892

    Affected versions: ≤ 3.1.4

    Fixed in: 3.1.5

    Severity: High 7.5 · Disclosed Apr 29, 2026

  • Otter - Gutenberg Block <= 3.1.0 - Unauthenticated Sensitive Information Exposure

    Information disclosure · CVE-2025-55715

    Affected versions: ≤ 3.1.0

    Fixed in: 3.1.1

    Severity: Medium 5.3 · Disclosed Aug 27, 2025

  • Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE <= 3.0.6 - Unauthetnicated Path Traversal to Arbitrary Image View

    Arbitrary file read or deletion · CVE-2024-11219

    Affected versions: ≤ 3.0.6

    Fixed in: 3.0.7

    Severity: Medium 5.3 · Disclosed Nov 26, 2024

  • Otter - Gutenberg Block <= 3.0.3 - Missing Authorization

    Missing authorization · CVE-2024-51671

    Affected versions: ≤ 3.0.3

    Fixed in: 3.0.4

    Severity: Medium 4.3 · Disclosed Nov 1, 2024

  • Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE <= 3.0.4 - Authenticated (Author+) Stored Cross-Site Scripting via SVG File Upload

    Cross-site scripting (XSS) · CVE-2024-10367

    Affected versions: ≤ 3.0.4

    Fixed in: 3.0.5

    Severity: Medium 6.4 · Disclosed Oct 31, 2024

  • Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE <= 2.6.9 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'titleTag'

    Cross-site scripting (XSS) · CVE-2024-3725

    Affected versions: ≤ 2.6.9

    Fixed in: 2.6.10

    Severity: Medium 6.4 · Disclosed Apr 16, 2024

  • Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE <= 2.6.8 - Authenticated (Contributor+) Stored Cross-Site Scripting via Block Attributes

    Cross-site scripting (XSS) · CVE-2024-3343

    Affected versions: ≤ 2.6.8

    Fixed in: 2.6.9

    Severity: Medium 6.4 · Disclosed Apr 10, 2024

  • Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE <= 2.6.8 - Authenticated (Author+) Limited File Upload to Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-3344

    Affected versions: ≤ 2.6.8

    Fixed in: 2.6.9

    Severity: Medium 6.4 · Disclosed Apr 10, 2024

  • Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE <= 2.6.5 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-2841

    Affected versions: ≤ 2.6.5

    Fixed in: 2.6.6

    Severity: Medium 6.4 · Disclosed Mar 28, 2024

  • Otter Blocks <= 2.6.5 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-2729

    Affected versions: ≤ 2.6.5

    Fixed in: 2.6.6

    Severity: Medium 6.4 · Disclosed Mar 28, 2024

  • Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE <= 2.6.4 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-2226

    Affected versions: ≤ 2.6.4

    Fixed in: 2.6.5

    Severity: Medium 6.4 · Disclosed Mar 13, 2024

  • ThemeIsle SDK <= Various Versions - Missing Authorization

    Missing authorization · CVE-2024-1047

    Affected versions: ≤ 2.6.2

    Fixed in: 2.6.3

    Severity: Medium 5.3 · Disclosed Feb 1, 2024

  • Otter - Gutenberg Blocks <= 2.2.5 - Authenticated (Author+) PHAR Deserialization

    PHP object injection · CVE-2023-2288

    Affected versions: ≤ 2.2.5

    Fixed in: 2.2.6

    Severity: High 8.8 · Disclosed May 2, 2023

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Oct 23, 2026.

Most common weaknesses in Otter Blocks

Cross-site scripting (XSS)

9 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

Missing authorization

6 issues

Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.

Information disclosure

2 issues

Data that should stay private, such as user details or configuration values, can be read from outside.

Frequently asked questions

Is Otter Blocks safe to use?

Otter Blocks is a well-known plugin with 300,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (3.2.11) and turn on automatic updates.

How do I find which version of Otter Blocks my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesOtter Blocks on WordPress.org