pretix-adyen stored XSS in payment API responses
Affects pretix-adyen before 1.5.5 in shops where Adyen API calls can be sent to an attacker-controlled server, because the returned results are embedded without escaping. Fixed in 1.5.5.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.5.5
- Who is exposed
- Specific setups only
Summary
A stored cross-site scripting flaw in pretix-adyen, a pretix product, lets a remote attacker with a low-privilege login run scripts in the shop without any action by the victim, which can lead to session takeover. The attacker configures their own ticket shop so that API calls go to an attacker-controlled server, and the responses are then embedded in the shop without proper escaping.
Written by a model
Original description
A stored XSS in pretix-adyen has been discovered where an attacker could configure his own ticket shop in a way that API calls are not made to Adyen, but an attacker-controlled server. Results of these API calls would then be embedded in a part of the shop without proper escaping, leading to full XSS including potential session takeover.
Who should check
Teams running the pretix-adyen plugin (Adyen payment integration) with pretix ticket shops, including self-hosted pretix installations.
“A stored XSS in pretix-adyen has been discovered”
What to do
Check whether your setup matches what the bug needs.
Affected: pretix-adyen, all currently supported versions (except the fixed versions listed in the advisory). The shop must be configured so that Adyen API calls go to an attacker-controlled server instead of Adyen. The returned results are embedded in a part of the shop without proper escaping.Upgrade to a fixed version: 1.5.5.
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-131163 (Stored XSS 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-131163 (entry last updated 2026-11-20):
Affected:
- PyPI package pretix-adyen: fixed in 1.5.5
Fixed versions: 1.5.5.
Conditions (all must be true for the bug to be hit):
- Affected: pretix-adyen, all currently supported versions (except the fixed versions listed in the advisory). (source: https://pretix.eu/about/en/blog/20261120-release-2026-9-3-adyen/)
- The shop must be configured so that Adyen API calls go to an attacker-controlled server instead of Adyen. (source: https://pretix.eu/about/en/blog/20261120-release-2026-9-3-adyen/)
- The returned results are embedded in a part of the shop without proper escaping. (source: https://pretix.eu/about/en/blog/20261120-release-2026-9-3-adyen/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-131163 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131163 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 the stack.check operation of the cve.now MCP server (execute) 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/20261120-release-2026-9-3-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-131163
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131163"}.Affected versions
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Affects PyPI packages
- Severity9.6/10CVSS 8.6, total technical impact per CISA
- 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 35 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | pretix.eu · about/en/blog/20261120-release-2026-9-3-adyen |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-131163 |
| Record | NVD · CVE-2026-131163 |
Questions about CVE-2026-131163
Is CVE-2026-131163 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
What does this mean?
Results returned from Adyen API calls are placed into a part of the shop without proper escaping, so injected script can run in the shop. The advisory says this leads to full cross-site scripting, including potential session takeover.
Source: pretix.eu
Which versions are affected by CVE-2026-131163?
pretix-adyen (PyPI): before 1.5.5.
Source: cve.now feed data
Am I affected, and how do I check?
All currently supported pretix-adyen versions before 1.5.5 are affected, except the fixed versions listed in the advisory. The setup requires the shop to send Adyen API calls to an attacker-controlled server instead of Adyen. Check the installed pretix-adyen version against 1.5.5 and review how the shop's Adyen API endpoint is configured.
Source: pretix.eu
How do I fix CVE-2026-131163?
Upgrade pretix-adyen to 1.5.5, the fixed version in the product range. No vendor patch identifiers are given in the checked facts.
Source: pretix.eu
Related
- CVE-2026-101275Insufficient validation of payment status in pretix-adyen
- CVE-2026-131167Unsafe usage of return values
- CVE-2026-130608When using the admin area profile form to change ones profile details except the password (so, email or username), the password field in…
- CVE-2026-101274When pretix is used as the identity provider in a Single-Sign-On (SSO) setup for customer accounts, the system did not properly validate…
- CVE-2026-127138Circumvention of offline barcode revocation check in pretixSCAN
- CVE-2026-131168Validation bypass allows buying sold-out products
No corrections so far. Something wrong on this page? Report an error.