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: 2026-02-16
Score: 7.5 High
EPSS: < 1% Very Low
KEV: No
Impact: Sensitive data exfiltration
Action: Apply Workaround
AI Analysis

Impact

emails sent by pretix use placeholders that are replaced with customer data; an attacker who can set email templates could craft names like {{event.__init__.__code__.co_filename}} to leak configuration files, database passwords, and API keys. The bug stems from inadequate validation of placeholder names, exposing the system to credential disclosure. The weakness corresponds to CWE-627, where untrusted input is used to evaluate code paths that can read sensitive data.

Affected Systems

The affected product is pretix, specifically the pretix and double_opt_in_step modules listed by the CNA. Version information is not disclosed in the available data, so any installation running these modules remains potentially vulnerable.

Risk and Exploitability

The vulnerability carries a CVSS score of 7.5, indicating a high severity. The EPSS score is below 1%, suggesting a low probability of exploitation at present. It is not listed in the CISA KEV catalog. An attacker must have the ability to modify email templates, which is typically granted to any backend user. Therefore, the risk is driven by the breadth of backend user privileges; restricting template editing or limiting backend access reduces the attack surface.

Generated by OpenCVE AI on April 18, 2026 at 12:07 UTC.

Remediation

Vendor Workaround

Limit backend access to trusted users, do not use user-controlled variables in the email templates.


OpenCVE Recommended Actions

  • Restrict backend access to trusted administrators only and disable user‑controlled template editing.
  • Ensure that no placeholders that could access internal variables are present in email templates or disable the double opt‑in step plugin until a fix is released.
  • Rotate all passwords and API keys contained in pretix.cfg as a precautionary measure.

Generated by OpenCVE AI on April 18, 2026 at 12:07 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 13 Mar 2026 12:45:00 +0000

Type Values Removed Values Added
First Time appeared Pretix double Opt In Step
Pretix pretix
CPEs cpe:2.3:a:pretix:double_opt_in_step:*:*:*:*:*:pretix:*:*
cpe:2.3:a:pretix:pretix:*:*:*:*:*:*:*:*
Vendors & Products Pretix double Opt In Step
Pretix pretix
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}


Tue, 17 Feb 2026 18:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Tue, 17 Feb 2026 09:00:00 +0000

Type Values Removed Values Added
First Time appeared Pretix
Pretix pretix-doistep
Vendors & Products Pretix
Pretix pretix-doistep

Mon, 16 Feb 2026 10:45:00 +0000

Type Values Removed Values Added
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.
Title Unsafe variable evaluation in email templates
Weaknesses CWE-627
References
Metrics cvssV4_0

{'score': 7.5, 'vector': 'CVSS: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'}


Subscriptions

Pretix Double Opt In Step Pretix Pretix-doistep
cve-icon MITRE

Status: PUBLISHED

Assigner: rami.io

Published:

Updated: 2026-02-17T17:06:30.536Z

Reserved: 2026-02-13T09:57:34.221Z

Link: CVE-2026-2451

cve-icon Vulnrichment

Updated: 2026-02-17T16:43:12.237Z

cve-icon NVD

Status : Analyzed

Published: 2026-02-16T11:15:56.290

Modified: 2026-03-13T12:39:56.690

Link: CVE-2026-2451

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-04-18T12:15:15Z

Weaknesses