Skip to main content
VulnerabilityPublished

CVE-2025-14882: pretix-offlinesales · Insecure Direct Object Reference

Affects pretix-offlinesalesSource CVE Database V5

0

Not known to be exploited · CVSS 3.8 Low.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 4.0 base score
3.8Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:U

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
PyPIpretix-offlinesalespkg:pypi/pretix-offlinesalesOther threatsAffected
  • =1.12.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until an official patch is released, European organizations should implement the following mitigations: 1) Restrict access to the pretix-offlinesales API endpoints to trusted networks and users only, minimizing exposure. 2) Monitor and audit API access logs for unusual access patterns or attempts to access files by UUIDs not owned by the requesting user. 3) Enforce strict user privilege management to limit the number of users with access to the vulnerable API. 4) Implement additional application-layer access controls or reverse proxies that validate user authorization before forwarding requests to the vulnerable endpoint. 5) Educate users and administrators about the risk and encourage strong credential hygiene to reduce the risk of account compromise. 6) Engage with the pretix vendor or community to obtain updates on patch availability and apply fixes promptly once released. 7) Consider temporary disabling or restricting the use of the offlinesales feature if feasible, to eliminate the attack surface.

Description

An API endpoint allowed access to sensitive files from other users by knowing the UUID of the file that were not intended to be accessible by UUID only.

References

Community reviews

Loading reviews…