CVE-2026-2892

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

2026-04-29 00:00
Drew Webber (mcdruid)

Strategic Overview

Status
Patched in 3.1.5
Affected Plugin
Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE
Affected Version
<= 3.1.4
CVSS
7.5High
Weakness type
CWE-285 · Improper Authorization
CVE
CVE-2026-2892
View all Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE vulnerabilities

At a glance

CVE-2026-2892 is a high-severity Improper Authorization vulnerability in the Otter Blocks WordPress plugin, affecting versions <= 3.1.4. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 3.1.5; sites on affected versions should update now. Disclosed April 2026, reported by Drew Webber (mcdruid).

Vulnerability Overview

The Otter Blocks plugin for WordPress is vulnerable to Purchase Verification Bypass in all versions up to, and including, 3.1.4. This is due to the 'get_customer_data' method relying on an unsigned 'o_stripe_data' cookie to determine Stripe product ownership for unauthenticated users. The 'check_purchase' method trusts this cookie data without performing server-side verification against the Stripe API for one-time 'payment' mode purchases. This makes it possible for unauthenticated attackers to bypass Stripe purchase-gated content visibility conditions by forging the 'o_stripe_data' cookie with a target product ID, which is publicly exposed in the checkout block's HTML source.

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. A successful exploit has high impact on confidentiality.

CWE-285: Improper Authorization

Otter Blocks <= 3.1.4 carries this weakness at get_customer_data, and reaching it takes no account at all. Improper authorization means a permission check exists but does not cover the case being exercised, so a caller who is allowed to do one thing is allowed to do a neighbouring thing as well.

A lower-privileged account performs an action reserved for a higher one, which on a multi-author or membership site means an ordinary user reaching administrative behaviour. For Otter Blocks the fix is 3.1.5: builds <= 3.1.4 are affected, anything from 3.1.5 onward is not.

Remediation

Update to version 3.1.5, 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.5 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-2892https://www.wordfence.com/threat-intel/vulnerabilities/id/3443950f-1f94-4e0b-8906-1a9b9602a746https://nvd.nist.gov/vuln/detail/CVE-2026-2892

Related records

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