Veille CVE

Recherche « themeisle Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE »

3 CVE

Critique 0 Élevée 1 Moyenne 1 Faible 1 Non évaluée 0 Exploitées (KEV) Tri : plus récentes « themeisle Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE » ✕
  1. CVE-2026-102002 3.1 Faible

    themeisle Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE

    The Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.2.6 via the 'otter_form_widget_filter' parameter. This makes it possible for authenticated attackers, with subscriber-level access and above, to extract the email addresses of the five most recent form submitters, their submission dates, and the site's total form submission count. The widget is registered whenever the themeisle_blocks_form_emails option is non-empty — the normal state after any Form block has been saved — meaning the exposure is active on any standard site using the plugin's form feature.

  2. CVE-2026-4945 5.3 Moyenne

    themeisle Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE

    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.

  3. CVE-2026-2892 7.5 Élevée

    themeisle Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE

    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.