Lucene search
+L

227 matches found

attackerkb
attackerkb
•added 2026/08/07 10:43 p.m.•22 views

CVE-2026-47127

Ghostfolio is an open source wealth management software. Prior to version 3.4.0, Ghostfolio's Stripe checkout success-URL handler at GET /api/v1/subscription/stripe/callback?checkoutSessionId= retrieves the Stripe Checkout Session by ID and unconditionally grants a Premium subscription to the...

6.5CVSS5.9AI score0.00338EPSS
SaveExploits0References3Affected Software1
Positive Technologies
Positive Technologies
•added 2026/07/31 12:00 a.m.•31 views

PT-2026-66698

Name of the Vulnerable Software and Affected Versions FlxWoo WordPress plugin versions prior to 3.1.1 Description The plugin fails to verify with the payment processor whether a checkout session was actually paid before marking the associated order as paid. This allows unauthenticated attackers t...

7.5CVSS5.7AI score0.00358EPSS
SaveExploits0References5
Vulnrichment
Vulnrichment
•added 2026/07/30 8:15 p.m.•19 views

CVE-2026-68500 Sylius Mollie Plugin: Payment status forgery via the payment webhook

Sylius Mollie Plugin provides Mollie payment integration for Sylius applications. Prior to 2.2.8, 3.2.4, and 3.3.1, Sylius Mollie Plugin's POST /locale/update-payment payment webhook accepts attacker-controlled id and orderId parameters but does not verify that the Mollie payment belongs to the...

7.5CVSS5.8AI score0.00681EPSS
SaveExploits0References10
Cvelist
Cvelist
•added 2026/07/30 8:15 p.m.•69 views

CVE-2026-68500 Sylius Mollie Plugin: Payment status forgery via the payment webhook

Sylius Mollie Plugin provides Mollie payment integration for Sylius applications. Prior to 2.2.8, 3.2.4, and 3.3.1, Sylius Mollie Plugin's POST /locale/update-payment payment webhook accepts attacker-controlled id and orderId parameters but does not verify that the Mollie payment belongs to the...

7.5CVSS0.00681EPSS
SaveExploits0References10
NVD
NVD
•added 2026/07/28 11:17 a.m.•26 views

CVE-2026-18029

Our payment integration with GiroCheckout did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one payment...

6.3CVSS0.00331EPSS
SaveExploits0References1
Vulnrichment
Vulnrichment
•added 2026/07/28 10:39 a.m.•25 views

CVE-2026-18029 Insufficient validation of payment status in pretix-girosolution

Our payment integration with GiroCheckout did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one payment...

6.3CVSS5.9AI score0.00331EPSS
SaveExploits0References1
attackerkb
attackerkb
•added 2026/07/28 10:39 a.m.•17 views

CVE-2026-18029

Our payment integration with GiroCheckout did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one payment...

6.3CVSS5.9AI score0.00331EPSS
SaveExploits0References2
CVE
CVE
•added 2026/07/28 10:39 a.m.•49 views

CVE-2026-18029

The CVE-2026-18029 entry is tied to the pretix-girosolution payment integration. Affected component: payment status validation in GiroCheckout flow. Root cause: insufficient validation of payment status responses, enabling an attacker to reuse a successful status for one payment with a different ...

6.3CVSS5.9AI score0.00331EPSS
SaveExploits0References1
Cvelist
Cvelist
•added 2026/07/28 10:39 a.m.•49 views

CVE-2026-18029 Insufficient validation of payment status in pretix-girosolution

Our payment integration with GiroCheckout did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one payment...

6.3CVSS0.00331EPSS
SaveExploits0References1
EUVD
EUVD
•added 2026/07/28 10:39 a.m.•29 views

EUVD-2026-49752

Our payment integration with GiroCheckout did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one payment...

6.3CVSS5.9AI score0.00331EPSS
SaveExploits0References1
Rapid7 Vulnerability Database (full)
Rapid7 Vulnerability Database (full)
•added 2026/07/28 12:00 a.m.•10 views

CVE-2026-18029: Improper Enforcement of Behavioral Workflow

Our payment integration with GiroCheckout did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one payment...

6.3CVSS5.8AI score0.00331EPSS
SaveExploits0References2
Positive Technologies
Positive Technologies
•added 2026/07/28 12:00 a.m.•29 views

PT-2026-65439

Our payment integration with GiroCheckout did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one payment...

6.3CVSS5.9AI score0.00331EPSS
SaveExploits0References2
NVD
NVD
•added 2026/07/11 7:16 a.m.•20 views

CVE-2026-11901

The WP Hotel Booking plugin for WordPress is vulnerable to Insufficient Verification of Data Authenticity in all versions up to, and including, 2.3.1. This is due to the webhookprocesspaypalstandard IPN handler selecting its PayPal validation endpoint from the attacker-controlled $REQUEST'testipn...

5.3CVSS0.00259EPSS
SaveExploits0References10
Positive Technologies
Positive Technologies
•added 2026/07/11 12:00 a.m.•31 views

PT-2026-57410

The WP Hotel Booking plugin for WordPress is vulnerable to Insufficient Verification of Data Authenticity in all versions up to, and including, 2.3.1. This is due to the web hook process paypal standard IPN handler selecting its PayPal validation endpoint from the attacker-controlled $ REQUEST'te...

5.3CVSS6.1AI score0.00259EPSS
SaveExploits0References10
osv_pysec
osv_pysec
•added 2026/07/07 2:34 p.m.•32 views

PYSEC-2026-1580 LNbits improperly handles potential network and payment failures when using Eclair backend

Summary Paying invoices in Eclair that do not get settled within the internal timeout about 30s lead to a payment being considered failed, even though it may still be in flight. Details Using blocking: true on the API call will lead to a timeout error if a payment does not get settled in the 30s...

8.1CVSS7.5AI score0.00602EPSS
SaveExploits0References5
PyPA
PyPA
•added 2026/07/07 2:34 p.m.•31 views

LNbits improperly handles potential network and payment failures when using Eclair backend

SummaryPaying invoices in Eclair that do not get settled within the internal timeout about 30s lead to a payment being considered failed, even though it may still be in flight. DetailsUsing blocking: true on the API call will lead to a timeout error if a payment does not get settled in the 30s...

8.1CVSS7.5AI score0.00602EPSS
SaveExploits0References5Affected Software1
Packet Storm
Packet Storm
•added 2026/06/29 12:00 a.m.•120 views

📄 WordPress WP Full Stripe Free 8.4.3 Missing Authorization

The WP Full Stripe Free plugin for WordPress is vulnerable to missing authorization in versions up to, and including, 8.4.3 via the wpfsupdatefailedpaymentstatus AJAX action. CVE-2026-12432: WP Full Stripe Free = 8.4.4 - Published: June 26, 2026 - Last Updated: June 27, 2026 - Researcher: Netwurm...

5.3CVSS5.8AI score0.00561EPSS
SaveExploits2
attackerkb
attackerkb
•added 2026/06/27 6:50 a.m.•26 views

CVE-2026-12432

The WP Full Stripe Free plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 8.4.3 via the wpfsupdatefailedpaymentstatus AJAX action. The handler is registered through both wpajax and wpajaxnopriv hooks and the underlying updatefailedpaymentstatus function...

5.3CVSS5.6AI score0.00561EPSS
SaveExploits2References11
NVD
NVD
•added 2026/06/25 3:16 p.m.•37 views

CVE-2026-57536

Our payment integration with Mollie did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one payment...

6.3CVSS0.00331EPSS
SaveExploits0References1
NVD
NVD
•added 2026/06/25 3:16 p.m.•32 views

CVE-2026-13222

Our payment integration with Oppwa-based payment methods did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one...

6.3CVSS0.00331EPSS
SaveExploits0References1
Rows per page
Query Builder