CVE-2026-97219 MStore API 4.21.1 - 4.22.0 - Subscriber+ Payment Bypass via 'status' Parameter

The MStore API WordPress plugin before 4.22.1 does not restrict which fields of an order a customer may update, allowing any authenticated user with a self-registerable account to change the status of their own unpaid order to a paid or fulfilled state and receive the goods without paying...

WordPress MStore API plugin 4.21.1-4.22.0 - Subscriber+ Payment Bypass vulnerability

Subscriber+ Payment Bypass vulnerability discovered by cyberkareem in WordPress Plugin MStore API versions 4.21.1-4.22.0...

WordPress Verge3D Publishing and E-Commerce plugin 4.1.0-4.13.0 - Unauthenticated Payment Bypass vulnerability

Unauthenticated Payment Bypass vulnerability discovered by Pablo González Pérez, Francisco José Ramírez Vicente, Iñigo Sánchez Enciso in WordPress Plugin Verge3D versions 4.1.0-4.13.0...

WordPress Paymattic plugin 4.6.20-4.6.25 - Unauthenticated Payment Bypass vulnerability

Unauthenticated Payment Bypass vulnerability discovered by Artus KG in WordPress Plugin Best Payments Plugin for WP versions 4.6.20-4.6.25...

WordPress Bookly plugin < 28.3 - Unauthenticated Payment Bypass vulnerability

Unauthenticated Payment Bypass vulnerability discovered by vuxvinh in WordPress Plugin Bookly versions 28.3...

CVE-2026-86838

The Bookly WordPress plugin before 28.3 does not validate client-supplied booking quantity values on the server before computing the appointment total, allowing unauthenticated users to reduce the total to zero and book paid services for free while bypassing the payment step...

CVE-2026-92996 Verge3D 4.1.0 - 4.13.0 - Unauthenticated Payment Bypass via v3d_payment_done

The Verge3D WordPress plugin from 4.1.0 through 4.13.0 does not verify with the payment provider that a payment was actually made, and does not check order ownership, allowing unauthenticated users to mark any order as paid...

CVE-2026-92996

The Verge3D WordPress plugin (versions 4.1.0 through 4.13.0 ) contains a vulnerability where it fails to verify payments with the payment provider and lacks order ownership checks. This allows unauthenticated users to mark any order as paid via the v3d_payment_done functionality. No specific reme...

CVE-2026-92996 Verge3D 4.1.0 - 4.13.0 - Unauthenticated Payment Bypass via v3d_payment_done

The Verge3D WordPress plugin from 4.1.0 through 4.13.0 does not verify with the payment provider that a payment was actually made, and does not check order ownership, allowing unauthenticated users to mark any order as paid...

CVE-2026-89411 Paymattic < 4.6.26 - Unauthenticated Payment Bypass via Unbound Stripe PaymentIntent

The Paymattic WordPress plugin from 4.6.20 before 4.6.26 does not verify that a confirmed Stripe payment belongs to the order it is applied to, allowing unauthenticated users to mark an arbitrary pending order as paid by confirming a smaller payment of their own against it...

CVE-2026-89411

The Paymattic WordPress plugin (versions 4.6.20 through 4.6.25) contains a vulnerability where it fails to verify that a confirmed Stripe payment corresponds to the specific order it is being applied to. This flaw allows unauthenticated users to perform an unauthenticated payment bypass by confir...

CVE-2026-89411 Paymattic < 4.6.26 - Unauthenticated Payment Bypass via Unbound Stripe PaymentIntent

The Paymattic WordPress plugin from 4.6.20 before 4.6.26 does not verify that a confirmed Stripe payment belongs to the order it is applied to, allowing unauthenticated users to mark an arbitrary pending order as paid by confirming a smaller payment of their own against it...

CVE-2026-86838 Bookly < 28.3 - Unauthenticated Payment Bypass via Booking Price Manipulation

The Bookly WordPress plugin before 28.3 does not validate client-supplied booking quantity values on the server before computing the appointment total, allowing unauthenticated users to reduce the total to zero and book paid services for free while bypassing the payment step...

CVE-2026-86838

The Bookly WordPress plugin before version 28.3 is vulnerable to an unauthenticated payment bypass . The root cause is a lack of server-side validation for client-supplied booking quantity values during the calculation of the appointment total. This allows unauthenticated users to manipulate the ...

EUVD-2026-88099

The Bookly WordPress plugin before 28.3 does not validate client-supplied booking quantity values on the server before computing the appointment total, allowing unauthenticated users to reduce the total to zero and book paid services for free while bypassing the payment step...

CVE-2026-86838 Bookly < 28.3 - Unauthenticated Payment Bypass via Booking Price Manipulation

The Bookly WordPress plugin before 28.3 does not validate client-supplied booking quantity values on the server before computing the appointment total, allowing unauthenticated users to reduce the total to zero and book paid services for free while bypassing the payment step...

CVE-2026-86838: External Control of Assumed-Immutable Web Parameter

The Bookly WordPress plugin before 28.3 does not validate client-supplied booking quantity values on the server before computing the appointment total, allowing unauthenticated users to reduce the total to zero and book paid services for free while bypassing the payment step...

WordPress Paymob for WooCommerce plugin < 4.1.14 - Unauthenticated Payment Bypass vulnerability

Unauthenticated Payment Bypass vulnerability discovered by Charles Vosburgh in WordPress Plugin Paymob for WooCommerce versions 4.1.14...

CVE-2026-87978 Paymob for WooCommerce < 4.1.14 - Unauthenticated Payment Bypass via Unverified Subscription Transaction Callback

The Paymob for WooCommerce WordPress plugin before 4.1.14 does not verify the request signature on one branch of its payment webhook, allowing unauthenticated attackers to mark arbitrary WooCommerce orders as paid without any payment...

CVE-2026-87978 Paymob for WooCommerce < 4.1.14 - Unauthenticated Payment Bypass via Unverified Subscription Transaction Callback

The Paymob for WooCommerce WordPress plugin before 4.1.14 does not verify the request signature on one branch of its payment webhook, allowing unauthenticated attackers to mark arbitrary WooCommerce orders as paid without any payment...