Insufficient validation of payment status in pretix-adyen
- Exploited
- No known exploitation
- Fix
- Fixed in 1.5.4
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.5.4.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 33/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The pretix-adyen plugin for pretix ticketing software fails to properly verify payment status responses from Adyen. Remotely, without logging in, an attacker can reuse a successful payment response from one payment for a different payment and obtain multiple valid tickets while paying only once.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Our payment integration with Adyen 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach10/20Affects PyPI packages
- Severity6.3/10CVSS 6.3
- No patch0/5No signal
What would change the score
- Would score about 78 if added to CISA KEV
- Would score about 73 if CISA's SSVC rates exploitation active
- Would score about 38 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.5.4.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-101275 (Insufficient validation of payment status in pretix-adyen), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-101275 (entry last updated 2026-11-10): Affected: - PyPI package pretix-adyen: fixed in 1.5.4 Fixed versions: 1.5.4. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-101275 is not listed as of cve.now's last read. This KEV status is for CVE-2026-101275 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Packages (PyPI): find every lockfile in each project and run check_stack from the cve.now MCP server on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies. Verify against the linked advisories before concluding, and cite the date you read each one: - https://pretix.eu/about/en/blog/20261110-adyen/ Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-101275 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-101275.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- pretix-adyenPyPI
fixed in 1.5.4
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-101275
Is CVE-2026-101275 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-101275?
pretix-adyen (PyPI): before 1.5.4.Source: cve.now feed data
How do I fix CVE-2026-101275?
Upgrade to a fixed version: 1.5.4.Source: cve.now feed data