VulnCrest
Search
Create account
Report an incident
Radar sectionsDatabase
Check my site
WordPress plugin

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

CVE-2026-2892Published · Updated

Action summary

Affected: ≤3.1.4Update to 3.1.5 or newer

All remediation steps
Watch plugin
Severity
High7.5
CVSS
7.5
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:H Confidentiality
High
I:N Integrity
None
A:N Availability
None
Weakness
CWE-285 Improper Authorization
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed
On this page8

Am I affected?

Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE otter-blocks

  1. Affected≤ 3.1.4
  2. Patched in3.1.5

Update to 3.1.5 or newer.

You are affected if you run ≤ 3.1.4. Version 3.1.5 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 3.1.5, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Drew Webber (mcdruid).

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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE

All 20
More vulnerabilities in Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE
SeverityVulnerabilityCVEPublished
Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting
<3.2.8Update to 3.2.8
CVE-2026-109933
Medium5.3Missing Authorization
<3.2.8Update to 3.2.8
CVE-2026-109935
High7.2Unauthenticated Stored Cross-Site Scripting
<3.2.8Update to 3.2.8
CVE-2026-109936
Medium5.33.2.7 - Missing Authorization
3.1.1 – 3.2.7Update to 3.2.8
CVE-2026-109934
Medium4.7Unauthenticated Open Redirect
≤3.2.2Update to 3.2.3
CVE-2026-109937

Timeline

  1. CVE published

    Severity high, CVSS 7.5

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
CVE® identifiers
[object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Jump to

Are you sure?