Limited HTML injection in emails
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2025.7.0, 2025.7.2, 2025.8.1, 2025.9.1, 2025.7.3, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- pretix
From 1.0.0 · fixed in 2025.7.0; From 2025.7.0 · fixed in 2025.7.2; From 2025.8.0 · fixed in 2025.8.1; From 2025.9.0 · fixed in 2025.9.1
- pretixPyPI
From 1.0.0 · fixed in 2025.7.2
- pretixPyPI
From 1.0.0 · fixed in 2025.7.3
- pretixPyPI
From 2025.8.0 · fixed in 2025.8.2
- pretixPyPI
From 2025.9.0 · fixed in 2025.9.2