Emails sent by pretix can utilize placeholders that will be filled with customer data. For example, when {name} is used in an email template, it will be replaced with the buyer's name for the final email. This mechanism contained a security-relevant bug: It was possible to exfiltrate information about the pretix system through specially crafted placeholder names such as {{event.__init__.__code__.co_filename}}. This way, an attacker with the ability to control email templates (usually every user of the pretix backend) could retrieve sensitive information from the system configuration, including even database passwords or API keys. pretix does include mechanisms to prevent the usage of such malicious placeholders, however due to a mistake in the code, they were not fully effective for this plugin. Out of caution, we recommend that you rotate all passwords and API keys contained in your pretix.cfg file.
oryginał ENCVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:L/U:RedPretix Double Opt In Step
APPPretix< 1.3.2Pretix
APPPretix4.16.0 – 2026.1.1 (bez)
Powiązane podatności
Nieprawidłowa walidacja plików w Pretix przed wersją 2024.1.1
Emails sent by pretix can utilize placeholders that will be filled with customer data. For example, when {name...
Emails sent by pretix can utilize placeholders that will be filled with customer data. For example, when {name...
Stored XSS in organizer and event settings of pretix up to 2024.7.0 allows malicious event organizers to injec...
A new API endpoint introduced in pretix 2025 that is supposed to return all check-in events of a specific eve...