CVE-2026-5600: A new API endpoint introduced in pretix 2025 that is supposed to return all check-in events of a specific event in fact returns all check-
Noroxi assessment
Priority: Monitor (action score 22/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.25% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: pretix pretix 2026.1.2, 2026.2.1, 2026.3.1.
Low priority for now. Upgrade to pretix pretix 2026.1.2, 2026.2.1, 2026.3.1 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
A new API endpoint introduced in pretix 2025 that is supposed to return all check-in events of a specific event in fact returns all check-in events belonging to the respective organizer. This allows an API consumer to access information for all other events under the same organizer, even those they should not have access to. These records contain information on the time and result of every ticket scan as well as the ID of the matched ticket. Example: { "id": 123, "successful": true, "error_reason": null, "error_explanation": null, "position": 321, "datetime": "2020-08-23T09:00:00+02:00", "list": 456, "created": "2020-08-23T09:00:00+02:00", "auto_checked_in": false, "gate": null, "device": 1, "device_id": 1, "type": "entry" } An unauthorized user usually has no way to match these IDs (position) back to individual people.
- Published
- Apr 8, 2026
- Updated
- Jul 24, 2026
- EPSS
- 0.2% · 17th percentile
- CWE
- CWE-653
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · rami.io
- 5.5
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:L/VI:N/VA:N/SC:H/SI:H/SA:H
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 pretix2025.10.0 and later · before 2026.1.2
- pretix pretix2026.2.0 and later · before 2026.2.1
- pretix pretix2026.3.0 and later · before 2026.3.1
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
- 2025.10.0 and later · before 2026.1.2affected · python
- 2026.2.0 and later · before 2026.2.1affected · python
- 2026.3.0 and later · before 2026.3.1affected · python
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 2025.10.0 · before 2026.1.2 | 2026.1.2 |
| PyPI | pretix | from 2026.2.0 · before 2026.2.1 | 2026.2.1 |
| PyPI | pretix | from 2026.3.0 · before 2026.3.1 | 2026.3.1 |
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-2025-14881Dec 19, 2025 · Insecure direct object reference15Monitor
- ← EarlierCVE-2026-2415Feb 16, 2026 · Unsafe variable evaluation in email templates30Monitor
- Later →CVE-2026-9712May 27, 2026 · Insecure direct object reference15Monitor
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 | 2026.1.2 | Vendor (CNA) |
| pretix pretix | 2026.2.1 | Vendor (CNA) |
| pretix pretix | 2026.3.1 | Vendor (CNA) |
| PyPI:pretix | 2026.1.2 | Package registry (OSV) |
| PyPI:pretix | 2026.2.1 | Package registry (OSV) |
| PyPI:pretix | 2026.3.1 | 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.
- Pratik Karanfinder
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.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-653 · Improper Isolation or CompartmentalizationCVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:L/VI:N/VA:N/SC:H/SI:H/SA:H/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
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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
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.