# CVE-2025-13742: Limited HTML injection in emails

> Attackers can inject HTML into emails via attendee names, enabling phishing by making malicious content appear trustworthy.

- **Severity:** Low 2.4 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Nov 2025
- **Updated:** 28 Nov 2025
- **Also known as:** GHSA-2mm6-624x-fqrr, PYSEC-2025-154

## What is CVE-2025-13742?

CVE-2025-13742 is a low-severity cross-site scripting vulnerability in pretix, published on 27 Nov 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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. 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.

Weakness: CWE-116 (Improper Encoding or Escaping of Output)

## Which versions are affected by CVE-2025-13742?

7 open source packages ship an affected version, including pretix. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pretix` | PyPI | From 1.0.0 | 2025.7.2 |
| `pretix` | PyPI | From 1.0.0 | 2025.7.3 |
| `pretix` | PyPI | From 1.0.0 | 2025.7.3 |
| `pretix` | PyPI | From 2025.8.0 | 2025.8.2 |
| `pretix` | PyPI | From 2025.8.0 | 2025.8.2 |
| `pretix` | PyPI | From 2025.9.0 | 2025.9.2 |
| `pretix` | PyPI | From 2025.9.0 | 2025.9.2 |

Products: Pretix Pretix.

## How do I fix CVE-2025-13742?

Upgrade pretix to a fixed version for your release line: 2025.7.2, 2025.7.3, 2025.8.2 or 2025.9.2.

## Is CVE-2025-13742 being exploited?

There is no known exploitation of CVE-2025-13742 in the wild and no public exploit code.

## Other vulnerabilities in pretix

- [CVE-2024-27447](https://insights.sbomify.com/CVE-2024-27447/): pretix mishandles file validation (critical 9.8)
- [CVE-2026-2415](https://insights.sbomify.com/CVE-2026-2415/): Unsafe variable evaluation in email templates (high 7.5)
- [CVE-2024-8113](https://insights.sbomify.com/CVE-2024-8113/): Stored XSS in Placeholder Samples in Mail Preview (high 7.2)
- [CVE-2026-5600](https://insights.sbomify.com/CVE-2026-5600/): pretix: API leaks check-in data between events of the same organizer (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-13742 and fix it if it is affected.

What it is: CVE-2025-13742 is a low-severity cross-site scripting vulnerability in pretix, published on 27 Nov 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-13742 in the wild and no public exploit code.

Affected packages and fixed versions:
- pretix (PyPI): affected from 1.0.0; fixed in 2025.7.2
- pretix (PyPI): affected from 1.0.0; fixed in 2025.7.3
- pretix (PyPI): affected from 1.0.0; fixed in 2025.7.3
- pretix (PyPI): affected from 2025.8.0; fixed in 2025.8.2
- pretix (PyPI): affected from 2025.8.0; fixed in 2025.8.2
- pretix (PyPI): affected from 2025.9.0; fixed in 2025.9.2
- pretix (PyPI): affected from 2025.9.0; fixed in 2025.9.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-13742/ (Markdown: https://insights.sbomify.com/CVE-2025-13742/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-13742
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-13742
- OSV: https://osv.dev/vulnerability/CVE-2025-13742

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-13742/
Summaries are generated and may contain mistakes; the official description above is the record.