PYSEC-2025-154
Vulnerability from pysec - Published: 2025-11-27 11:15 - Updated: 2026-05-20 09:19Emails 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.
| Name | purl | pretix | pkg:pypi/pretix |
|---|
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "pretix",
"purl": "pkg:pypi/pretix"
},
"ranges": [
{
"events": [
{
"introduced": "1.0.0"
},
{
"fixed": "2025.7.2"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.0.0",
"1.1.0",
"1.1.1",
"1.1.2",
"1.1.3",
"1.10.0",
"1.10.1",
"1.11.0",
"1.11.1",
"1.12.0",
"1.12.1",
"1.13.0",
"1.13.1",
"1.14.0",
"1.15.0",
"1.15.1",
"1.15.2",
"1.16.0",
"1.17.0",
"1.17.1",
"1.2.0",
"1.2.1.post2",
"1.2.2",
"1.3.0",
"1.3.0.post1",
"1.3.1",
"1.4.0",
"1.4.1",
"1.5.0",
"1.5.1",
"1.5.2",
"1.6.0",
"1.6.1",
"1.6.2",
"1.7.1",
"1.7.2",
"1.8.0",
"1.8.1",
"1.9.0",
"1.9.1",
"2.0.0",
"2.1.0",
"2.2.0",
"2.3.0",
"2.4.0",
"2.5.0",
"2.6.0",
"2.7.0",
"2.7.1",
"2.7.2",
"2.8.2",
"2023.10.0",
"2023.10.1.post1",
"2023.10.2",
"2023.6.0",
"2023.6.1",
"2023.6.3",
"2023.7.0",
"2023.7.1",
"2023.7.3",
"2023.8.0",
"2023.8.1",
"2023.9.0",
"2023.9.1",
"2024.1.0",
"2024.1.1",
"2024.10.0",
"2024.11.0",
"2024.2.0",
"2024.3.0",
"2024.4.0",
"2024.5.0",
"2024.5.1",
"2024.6.0",
"2024.6.1",
"2024.7.0",
"2024.7.1",
"2024.8.0",
"2024.9.0",
"2025.1.0",
"2025.2.0",
"2025.3.0",
"2025.4.0",
"2025.5.0",
"2025.6.0",
"2025.7.0",
"2025.7.1",
"3.0.0",
"3.0.1",
"3.1.0",
"3.10.0",
"3.11.0",
"3.11.1",
"3.12.0",
"3.12.1",
"3.13.0",
"3.13.1",
"3.14.0",
"3.14.1",
"3.14.2",
"3.15.0",
"3.16.0",
"3.17.1",
"3.17.2",
"3.18.0",
"3.2.0",
"3.3.0",
"3.4.0",
"3.5.0",
"3.6.0",
"3.6.0.post1",
"3.7.0",
"3.8.0",
"3.9.0",
"4.0.0",
"4.1.0",
"4.10.0",
"4.10.1",
"4.11.0",
"4.11.1",
"4.12.0",
"4.13.0",
"4.13.1",
"4.14.0",
"4.14.0.dev0",
"4.15.0",
"4.15.0.dev0",
"4.15.1",
"4.16.0",
"4.16.1",
"4.17.0",
"4.17.1",
"4.18.0",
"4.18.1",
"4.18.2",
"4.18.2.post1",
"4.19.0",
"4.2.0",
"4.20.0",
"4.20.1",
"4.20.2.post1",
"4.20.4",
"4.3.0",
"4.3.1",
"4.4.0",
"4.4.1",
"4.5.0",
"4.5.1",
"4.5.2",
"4.6.0",
"4.6.1",
"4.7.0",
"4.7.1",
"4.8.0",
"4.9.0",
"4.9.1"
]
}
],
"aliases": [
"CVE-2025-13742",
"GHSA-2mm6-624x-fqrr"
],
"details": "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\u0027s 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.",
"id": "PYSEC-2025-154",
"modified": "2026-05-20T09:19:11.509307Z",
"published": "2025-11-27T11:15:47.760Z",
"references": [
{
"type": "ARTICLE",
"url": "https://pretix.eu/about/en/blog/20251126-release-2025-9-1/"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-2mm6-624x-fqrr"
}
],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.