# CVE-2026-2892: Otter Blocks <= 3.1.4 - Improper Authorization to Unauthenticated Purchase Verification Bypass via Forged Cookie

> Unauthenticated attackers can bypass purchase verification by forging a cookie to access gated content in the Otter Blocks WordPress plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Apr 2026
- **Updated:** 1 May 2026
- **Also known as:** GHSA-h3rm-xcqx-mv7q

## What is CVE-2026-2892?

CVE-2026-2892 is a high-severity authentication bypass vulnerability in themeisle Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE, published on 30 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2026-2892?


## How do I fix CVE-2026-2892?

No fix has been published for CVE-2026-2892 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-2892 being exploited?

There is no known exploitation of CVE-2026-2892 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-2892 and fix it if it is affected.

What it is: CVE-2026-2892 is a high-severity authentication bypass vulnerability in themeisle Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE, published on 30 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2892 in the wild and no public exploit code.

Affected product: themeisle Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-2892/ (Markdown: https://insights.sbomify.com/CVE-2026-2892/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-2892
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2892
- OSV: https://osv.dev/vulnerability/CVE-2026-2892

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-2892/
Summaries are generated and may contain mistakes; the official description above is the record.