Monitor vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
7.5
Pretix exposes sensitive system data through emails
CVE-2026-2451
Summary
A bug in Pretix's email placeholder feature allowed attackers to extract sensitive system information, including passwords and API keys. This was possible through specially crafted placeholder names. We recommend rotating all passwords and API keys in your Pretix config file to be safe.
What to do
No fix is available yet. Check with your software vendor for updates.
Affected software
| Vendor | Product | Affected versions | Fix available |
|---|---|---|---|
| pretix | double_opt_in_step | <= 1.3.2 | – |
| pretix | pretix | > 4.16.0 , <= 2026.1.1 | – |
Original title
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 fi...
Original 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.
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.
nvd CVSS4.0
7.5
Vulnerability type
CWE-627
Published: 16 Feb 2026 · Updated: 14 Mar 2026 · First seen: 6 Mar 2026