CVE-2026-13225
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 · uneditedMalicious HTML content could be injected into the email address of an order, which pretix showed without sanitization on the confirmation page for individual tickets in that order.
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 confidenceThis is a stored Cross-Site Scripting (XSS) vulnerability in pretix where malicious HTML injected into an order's email address field is rendered without sanitization on the ticket confirmation page. When other users view the confirmation page, the embedded script executes in their browser context.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Authentication
- X
- User interaction
- P
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L/E:X/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
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 checksWork through these to decide whether this CVE applies to you.
-
Identify pretix installation and versionCheck your pretix installation directory for a version file or run 'pip show pretix' to retrieve the installed version numberAffected if The installed pretix version falls within the range containing this vulnerability (compare your version to the affected release)
-
Locate the ticket confirmation page templateSearch the pretix codebase for templates that render order confirmation pages, typically named something like 'confirmation.html' or 'order.html' in the templates directoryAffected if A confirmation page template exists that displays order details including the email address field
-
Inspect email address rendering in the templateOpen the confirmation template and locate where the order's email address is output (search for 'email' or 'attendee.email' in the template)Affected if The email field is rendered using raw output (e.g., {{ order.email }} or {{ attendee.email }}) without any encoding filter like '|escape' or '|html'
-
Check for output encoding on user-supplied fieldsReview the template code around the email output to see if HTML encoding functions are applied, such as '|escape', '|safe', or template auto-escaping is disabled for that sectionAffected if No HTML encoding/escaping filter is applied to the email field output, allowing raw HTML to be rendered
-
Verify the vulnerability with a test orderCreate a test order with a deliberately crafted email address containing HTML/JavaScript (e.g., '<script>alert(1)</script>@test.com') and view the confirmation page to see if the script executesAffected if The injected script executes or the raw HTML is visible in the page source, confirming the XSS vulnerability is present
You are affected if you run pretix with a vulnerable version AND the email address field on the ticket confirmation page is rendered without HTML encoding, allowing stored XSS to execute when others view the confirmation page.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement output encoding/sanitization (HTML encoding) on the email address field when rendering it on the confirmation page to prevent script execution.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13225 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-13225 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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