CVE-2025-13742
Limited HTML injection in emails
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.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Passive
What an attacker can affect
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
Exploit likelihood
What each source reports
CVE List Score used
2.4
Limited HTML injection in emails
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.
- Record
CVE-2025-13742- CVSS 4.0
- 2.4 Low
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:L/VA:L/SC:N/SI:L/SA:L/E:U - Weakness
- CWE-116
- Updated
- 2026-11-02
EUVDEUVD-2025-199816
2.4
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.
- Record
EUVD-2025-199816- CVSS 4.0
- 2.4 Low
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:L/VA:L/SC:N/SI:L/SA:L/E:U - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-2mm6-624x-fqrr
2.4
pretix has Email Content Injection Through Maliciously Formatted Names
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.
- Record
GHSA-2mm6-624x-fqrr- CVSS 4.0
- 2.4 Low
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:L/VA:L/SC:N/SI:L/SA:L/E:U - Weakness
- CWE-116
- Updated
- 2026-11-02
NVD
2.4
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.
- Record
CVE-2025-13742- CVSS 4.0
- 2.4 Low
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:L/VA:L/SC:N/SI:L/SA:L/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X - CVSS 3.1
- 6.1 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N - Weakness
- CWE-116
- Updated
- 2026-11-02
OSV
2.4
Limited HTML injection in emails
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.
- Record
CVE-2025-13742- CVSS 4.0
- 2.4 Low
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:L/VA:L/SC:N/SI:L/SA:L/E:U - Updated
- 2026-11-02
OSVGHSA-2mm6-624x-fqrr
2.4
pretix has Email Content Injection Through Maliciously Formatted Names
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.
- Record
GHSA-2mm6-624x-fqrr- CVSS 4.0
- 2.4 Low
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:L/VA:L/SC:N/SI:L/SA:L/E:U - Weakness
- CWE-116
- Updated
- 2026-11-02
OSVPYSEC-2025-154
6.1
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.
- Record
PYSEC-2025-154- CVSS 3.1
- 6.1 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N - Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
pretixPyPI |
1.0.0 up to 2025.7.3 | 2025.7.3 |
pretixPyPI |
2025.8.0 up to 2025.8.2 | 2025.8.2 |
pretixPyPI |
2025.9.0 up to 2025.9.2 | 2025.9.2 |
pretixPyPI |
1.0.0 up to 2025.7.3, plus listed versions 1.1.01.1.11.1.21.1.31.10.0 Show 45 moreShow less1.10.11.11.01.11.11.12.01.12.11.13.01.13.11.14.01.15.01.15.11.15.21.16.01.17.01.17.11.2.01.2.1.post21.2.21.3.01.3.0.post11.3.11.4.01.4.11.5.01.5.11.5.21.6.01.6.11.6.21.7.11.7.21.8.01.8.11.9.01.9.12.0.02.1.02.2.02.3.02.4.02.5.02.6.02.7.02.7.12.7.22.8.2 |
2025.7.3 |
pretixPyPI |
2025.8.0 up to 2025.8.2, plus listed versions 2025.8.1 |
2025.8.2 |
pretixPyPI |
2025.9.0 up to 2025.9.2, plus listed versions 2025.9.1 |
2025.9.2 |
pretixPyPI |
1.0.0 up to 2025.7.2, plus listed versions 1.1.01.1.11.1.21.1.31.10.0 Show 45 moreShow less1.10.11.11.01.11.11.12.01.12.11.13.01.13.11.14.01.15.01.15.11.15.21.16.01.17.01.17.11.2.01.2.1.post21.2.21.3.01.3.0.post11.3.11.4.01.4.11.5.01.5.11.5.21.6.01.6.11.6.21.7.11.7.21.8.01.8.11.9.01.9.12.0.02.1.02.2.02.3.02.4.02.5.02.6.02.7.02.7.12.7.22.8.2 |
2025.7.2 |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2025-13742 is a low vulnerability (CVSS 2.4) in Pretix, published November 27, 2025. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.19%, the 9th percentile. Fixed in pretix 2025.7.3.
References
pretix.eu/about/en/blog/20251126-release-2025-9-1
nvd.nist.gov/vuln/detail/CVE-2025-13742
github.com/pypa/advisory-database/tree/main/vulns/pretix/PYSEC-2025-154.yaml
pretix.eu/about/en/security
web.archive.org/web/20251129201933/https://pretix.eu/about/en/blog/20251127-release-2025-9-2
github.com/advisories/GHSA-2mm6-624x-fqrr
pypi.org
github.com/CVEProject/cvelistV5/tree/main/cves/2025/13xxx/CVE-2025-13742.json
github.com/pretix/pretix
Left out here: 211 versions. The JSON record has them.