Technical impact
The flaw occurs when pretix is used as an identity provider in an SSO configuration for customer accounts. The system fails to verify that the `response_type` requested in an authorization request matches the grant type allowed for the SSO client. If a client is configured to allow only the `code` response type, which requires knowledge of the client secret, it can nonetheless request a different type such as `id_token`. The server accepts that request and issues a valid token, effectively bypassing the intended security restriction.
Affected Systems
Any deployment of pretix that functions as the identity provider in an SSO setup is potentially affected. The vulnerable behavior applies to SSO clients that have been configured to restrict the `response_type` to `code`. No specific product version is listed in the CNA data, so all releases with this logic are at risk unless a patch has been applied.
Risk and Exploitability
The CVSS score of 6.9 indicates a moderate severity. The EPSS score is 0.00392 (<1%), and the vulnerability is not listed in the CISA KEV catalog, suggesting it is not currently a widely exploited issue. An attacker must be able to execute JavaScript on a page that matches one of the redirect URIs configured for the compromised client. Once that occurs, the attacker can extract the token issued for an unintended response type. The likely attack vector involves XSS or compromised redirect pages, and the impact is the unauthorized ability to obtain bearer tokens granting access to user resources.