CVE-2025-13742: Limited HTML injection in emails
Noroxi assessment
Priority: Monitor (action score 9/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No special conditions are required; it is repeatable.
- Fixed version: pretix pretix 2025.10.0, 2025.7.0, 2025.7.2.
Low priority for now. Upgrade to pretix pretix 2025.10.0, 2025.7.0, 2025.7.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Nov 27, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- CWE-116
Report tools
Action score
9
Monitor
Low priority for now.
- CVSS
- 9 / 40 · 2.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · rami.io
- 2.4
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| pretix | pretix | cpe:2.3:a:pretix:pretix |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- pretix pretix1.0.0 and later · before 2025.7.2
- pretix pretix2025.8.0
- pretix pretix2025.9.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (rami.io). Independent of NVD's CPE analysis and usually ahead of it.
pretix pretix
- 1.0.0 and later · before 2025.7.0affected · python
- 2025.7.0 and later · before 2025.8.0affected · pythonfixed in 2025.7.2
- 2025.8.0 and later · before 2025.9.0affected · pythonfixed in 2025.8.1
- 2025.9.0 and later · before 2025.10.0affected · pythonfixed in 2025.9.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| PyPI | pretix | from 1.0.0 · before 2025.7.3 | 2025.7.3 |
| PyPI | pretix | from 1.0.0 · before 2025.7.2 | 2025.7.2 |
| PyPI | pretix | from 2025.8.0 · before 2025.8.2 | 2025.8.2 |
| PyPI | pretix | from 2025.9.0 · before 2025.9.2 | 2025.9.2 |
Same product
pretix: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-27447pretix before 2024.1.1 mishandles file validation.39Monitor
- CVE-2026-57532Malicious HTML content contained in the layout specification of a PDF
ticket or badge layout was executed when the PDF editor is opened in…35Monitor
- CVE-2026-13602Session takeover vulnerability30Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-8113Aug 23, 2024 · Stored XSS in Placeholder Samples in Mail Preview28Monitor
- Later →CVE-2025-14881Dec 19, 2025 · Insecure direct object reference15Monitor
- Later →CVE-2026-2415Feb 16, 2026 · Unsafe variable evaluation in email templates30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| pretix pretix | 2025.10.0 | Vendor (CNA) |
| pretix pretix | 2025.7.0 | Vendor (CNA) |
| pretix pretix | 2025.7.2 | Vendor (CNA) |
| pretix pretix | 2025.8.0 | Vendor (CNA) |
| pretix pretix | 2025.8.1 | Vendor (CNA) |
| pretix pretix | 2025.9.0 | Vendor (CNA) |
| pretix pretix | 2025.9.1 | Vendor (CNA) |
| PyPI:pretix | 2025.7.2 | Package registry (OSV) |
| PyPI:pretix | 2025.7.3 | Package registry (OSV) |
| PyPI:pretix | 2025.8.2 | Package registry (OSV) |
| PyPI:pretix | 2025.9.2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Jan Roring (binsec GmbH)finder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- P
- Scope
- X
Weakness class (CWE)
CWE-116 · Improper Encoding or Escaping of OutputCVSS vector
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
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.