dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2026-2892

HIGH · 7.5 CVSS v3.1 Published 2026-04-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Otter Blocks WordPress plugin up to version 3.1.4 uses an unsigned 'o_stripe_data' cookie in its 'get_customer_data' method to verify Stripe product ownership for unauthenticated users. The 'check_purchase' method trusts this client-side cookie data without performing server-side validation against the Stripe API for one-time payment mode purchases. Attackers can forge this cookie with a product ID (found in plain HTML on checkout blocks) to bypass purchase-gated content restrictions.

MitigationReplace cookie-based purchase verification with server-side Stripe API validation. Implement cryptographic signing or encryption for any client-side data, or preferably use server-side session/state management tied to verified Stripe webhook events or API calls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Otter Blocks plugin installation and version
    Check the installed Otter Blocks plugin version in WordPress via Plugins admin page, plugin header comments in otter-blocks.php, or by running: wp plugin list | grep otter-blocks
    Affected if Plugin version is 3.1.4 or lower (any version up to and including 3.1.4)
  2. Identify if Stripe checkout blocks are in use
    Review WordPress pages/posts for Otter Blocks checkout, payment, or product blocks that integrate with Stripe. Check block content in the editor or page HTML for stripe-related block types.
    Affected if Otter Blocks checkout or payment blocks with Stripe integration are present on the site
  3. Inspect for the vulnerable o_stripe_data cookie
    Visit a checkout page using Otter Blocks Stripe integration and inspect browser cookies. Look for a cookie named 'o_stripe_data' being set during the checkout flow.
    Affected if The o_stripe_data cookie is present and used for purchase verification without server-side validation
  4. Check for exposed product IDs in checkout HTML
    View the source HTML of any Otter Blocks checkout page and search for product IDs in plain HTML (visible in data attributes, hidden fields, or block markup).
    Affected if Product IDs are visible in plaintext HTML on checkout pages, making forgery possible

A site is affected if it runs Otter Blocks plugin version 3.1.4 or lower and uses Stripe checkout/payment blocks, which rely on the client-side o_stripe_data cookie without server-side Stripe API validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace cookie-based purchase verification with server-side Stripe API validation. Implement cryptographic signing or encryption for any client-side data, or preferably use server-side session/state management tied to verified Stripe webhook events or API calls.

Recommended fix Moderate confidence

Update to Otter Blocks version 3.1.5 or latest available version

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Otter Blocks' in the plugin list
  4. Click 'Update now' if an update is available, or manually upload the latest version from wordpress.org/plugins/otter-blocks/
  5. After update, verify the plugin version is 3.1.5 or higher under Plugins > Installed Plugins

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2892 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2892 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data