← CVE index
Vulnerability record/PUBLISHED/Published Nov 20, 2026 11:29:20 UTC

CVE-2026-131170

Our payment integration with Stripe 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. However, the attack requires knowledge of a valid charge ID from the same event which we believe is usually not exposed to users. To simplify attack surface, the fix removes support for incoming webhooks regarding payments created through Stripe's old "source" API. pretix stopped creating payments using this API in 2024.1 for most payment methods and in 2024.9 for all payment methods.

Base score6.3/ 10
SeverityMediumCVSS 4.0

Exploitability / impact

CVSS metric breakdown

Vector-derived attributes
Base severityMedium
Attack vectorNetworkAV
Attack complexityLowAC
Attack requirementsPresentAT
Privileges requiredNonePR
User interactionNoneUI
Vulnerable system confidentialityNoneVC
Vulnerable system integrityLowVI
Vulnerable system availabilityNoneVA
Subsequent system confidentialityNoneSC
Subsequent system integrityNoneSI
Subsequent system availabilityNoneSA
CVSS vector stringCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

CVSS communicates standardized severity and impact characteristics. It does not establish whether a system is exploitable in your specific environment.

Record context

CVE Numbering Authoritypretix
Last updatedNov 20, 2026 11:29:20 UTC
PublishedNov 20, 2026 11:29:20 UTC
ReservedNov 17, 2026 20:25:12 UTC

Credits

  • Aaron Sagman
  • bowolalix