Stored XSS in pretix-adyen
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| pretix | pretix-adyen | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Pretix | Pretix-adyen |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.527% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-79 |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Pretix
Pretix pretix-adyen |
|
| Vendors & Products |
Pretix
Pretix pretix-adyen |
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Stored XSS in pretix-adyen | |
| References |
| |
| Metrics |
cvssV4_0
|