CVE-2026-4945

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

2026-09-06 00:00
Dmitrii Ignatyev

Strategic Overview

Status
Patched in 3.1.8
Affected Plugin
Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE
Affected Version
<= 3.1.7
CVSS
5.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-4945
View all Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE vulnerabilities

At a glance

CVE-2026-4945 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Otter Blocks WordPress plugin, affecting versions <= 3.1.7. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.1.8; sites on affected versions should update now. Disclosed September 2026, reported by Dmitrii Ignatyev.

Vulnerability Overview

The Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.1.7 via the 'watch_checkout' function due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to pay for a lower-cost product while obtaining entitlement for a premium product by manipulating the product_id parameter independently of the price_id parameter in the Stripe checkout URL.

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.

CWE-639: Authorization Bypass Through User-Controlled Key

Otter Blocks <= 3.1.7 carries this weakness at watch_checkout, and reaching it takes no account at all. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Otter Blocks the fix is 3.1.8: builds <= 3.1.7 are affected, anything from 3.1.8 onward is not.

Remediation

Update to version 3.1.8, 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.8 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-4945https://www.wordfence.com/threat-intel/vulnerabilities/id/7ecb9f61-68d5-4c70-8d7d-e4fb067fcff9https://nvd.nist.gov/vuln/detail/CVE-2026-4945

Related records

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