dbcve.org
PretixApplication

CVE-2025-13742

MEDIUM · 6.1 CVSS v3.1 Published 2025-11-27
Fix available
A fix is available. Upgrade to 2025.7.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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. If the name of the attendee contained HTML or Markdown formatting, this was rendered as HTML in the resulting email. This way, a user could inject links or other formatted text through a maliciously formatted name. Since pretix applies a strict allow list approach to allowed HTML tags, this could not be abused for XSS or similarly dangerous attack chains. However, it can be used to manipulate emails in a way that makes user-provided content appear in a trustworthy and credible way, which can be abused for phishing.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In pretix, email templates support placeholders like {name} that get replaced with customer data. When attendee names contain HTML or Markdown formatting, this was rendered as HTML in the resulting email. Although a strict allowlist prevents XSS, user-supplied content could appear as legitimate formatted links and text, enabling phishing attacks where malicious content appears trustworthy.

MitigationStrip HTML/Markdown from user-supplied data before rendering in email templates, or explicitly escape all user input in the email context to prevent user content from appearing as system-generated content.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PretixApplication
Affected:>= 1.0.0, < 2025.7.2= 2025.8.0= 2025.9.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed pretix version
    Check the installed pretix version via package manager (pip show pretix) or the admin interface under 'System' > 'Settings' > 'General'. Compare this version number against the affected ranges: >= 1.0.0 and < 2025.7.2, or exactly 2025.8.0, or exactly 2025.9.0.
    Affected if The installed version falls within any of these ranges: >=1.0.0 and <2025.7.2, or =2025.8.0, or =2025.9.0
  2. Verify email template usage
    In the pretix admin panel, navigate to 'Email' > 'Templates' and identify any email templates that contain placeholders such as {name}, {attendee_name}, or similar customer data placeholders.
    Affected if Email templates with customer data placeholders exist and are active
  3. Check attendee input mechanism
    Review the event configuration to determine how attendee names are collected. This could be via the pretix frontend, third-party plugins, or imported from external sources.
    Affected if Attendee names can be submitted via forms, imports, or third-party integrations without HTML/Markdown stripping at input time
  4. Inspect email rendering output
    Send a test email using an attendee name containing HTML-like content (for example: '<a href="http://example.com">Click here</a>' or '**bold text**' in Markdown). Examine the received email to see if this content is rendered as formatted HTML/Markdown rather than escaped plaintext.
    Affected if User-supplied name content appears as rendered HTML or Markdown formatting in the delivered email (rather than being escaped to harmless plaintext)

You are affected if your pretix version is in the affected ranges AND you use email templates with customer data placeholders AND user-supplied content can contain HTML/Markdown that gets rendered as formatting in outgoing emails.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2025.7.2 or later
Fixed in 2025.7.2
Interim mitigation

Strip HTML/Markdown from user-supplied data before rendering in email templates, or explicitly escape all user input in the email context to prevent user content from appearing as system-generated content.

Recommended fix High confidence

pretix >= 2025.10.0

  1. 1. Identify the current pretix version by checking the installed package or admin interface
  2. 2. If running a version < 2025.7.2, or exactly 2025.8.0 or 2025.9.0, plan an upgrade
  3. 3. Upgrade pretix to version 2025.10.0 or later, which contains the fix for HTML injection in email placeholders
  4. 4. After upgrade, verify email templates still function correctly with placeholder replacements
  5. 5. Test by creating a test attendee with HTML/Markdown in the name field and confirm it is now properly escaped in email output

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pretix Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13742 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13742 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data