# CVE-2025-14881: Insecure direct object reference

> Attackers can access other users' sensitive files by guessing UUIDs due to missing authorization checks on API endpoints.

- **Severity:** Low 3.8 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Dec 2025
- **Updated:** 19 Dec 2025
- **Also known as:** GHSA-r2h2-g46h-8mx8, PYSEC-2026-1803

## What is CVE-2025-14881?

CVE-2025-14881 is a low-severity missing authorization vulnerability in pretix, published on 19 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple API endpoints 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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

7 open source packages ship an affected version, including pretix.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pretix` | PyPI | All versions | 2025.8.3, 2025.9.3, 2025.10.1 |
| `pretix` | PyPI | All versions | 2025.8.3 |
| `pretix` | PyPI | All versions | 2025.8.3 |
| `pretix` | PyPI | From 2025.10.0 | 2025.10.1 |
| `pretix` | PyPI | From 2025.10.0 | 2025.10.1 |
| `pretix` | PyPI | From 2025.9.0 | 2025.9.3 |
| `pretix` | PyPI | From 2025.9.0 | 2025.9.3 |

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

Upgrade pretix to a fixed version for your release line: 2025.8.3, 2025.9.3 or 2025.10.1.

## Is CVE-2025-14881 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14881 is a low-severity missing authorization vulnerability in pretix, published on 19 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-14881 in the wild and no public exploit code.

Affected packages and fixed versions:
- pretix (PyPI): affected all versions; fixed in 2025.8.3, 2025.9.3, 2025.10.1
- pretix (PyPI): affected all versions; fixed in 2025.8.3
- pretix (PyPI): affected all versions; fixed in 2025.8.3
- pretix (PyPI): affected from 2025.10.0; fixed in 2025.10.1
- pretix (PyPI): affected from 2025.10.0; fixed in 2025.10.1
- pretix (PyPI): affected from 2025.9.0; fixed in 2025.9.3
- pretix (PyPI): affected from 2025.9.0; fixed in 2025.9.3

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-14881/ (Markdown: https://insights.sbomify.com/CVE-2025-14881/index.md)
```

## Sources

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

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