Home

Description

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.

PUBLISHED Reserved 2026-02-13 | Published 2026-02-16 | Updated 2026-02-17 | Assigner rami.io




HIGH: 7.5CVSS: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/RE:L/U:Red

Problem types

CWE-627 Dynamic Variable Evaluation

Product status

Default status
unaffected

1.0.0 (python) before 1.3.2
affected

References

pretix.eu/about/en/blog/20260216-release-2026-1-1/ vendor-advisory

cve.org (CVE-2026-2451)

nvd.nist.gov (CVE-2026-2451)

Download JSON