dbcve.org
PretixApplication · Rami

CVE-2023-27891

HIGH · 7.5 CVSS v3.1 Published 2023-03-06
Fix available
A fix is available. Upgrade to 4.15.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
rami.io pretix before 4.17.1 allows OAuth application authorization from a logged-out session. The fixed versions are 4.15.1, 4.16.1, and 4.17.1.

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 confidence

pretix before version 4.17.1 contains an OAuth authentication bypass where the authorization endpoint fails to properly validate the user's session state, allowing OAuth app authorization from a logged-out session. This could enable an attacker to trick authenticated users into authorizing malicious third-party applications.

MitigationUpgrade pretix to version 4.15.1, 4.16.1, or 4.17.1 to ensure proper session validation during OAuth authorization flows.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PretixApplication
Affected:>= 1.16.0, < 4.15.1= 4.16.0= 4.17.0

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
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed pretix version
    Check the pretix installation by viewing the version file, running 'pip show pretix' or checking the admin dashboard version info. Compare against affected ranges: >= 1.16.0 and < 4.15.1, or exactly version 4.16.0 or 4.17.0
    Affected if The installed version falls within >= 1.16.0 and < 4.15.1, or is exactly 4.16.0 or 4.17.0
  2. Verify OAuth authentication is enabled
    Check if the pretix instance has OAuth support enabled. This can be done by reviewing the pretix settings in the admin panel under 'OAuth settings' or by checking the configuration file for 'socialauth' or 'oauth' related settings
    Affected if OAuth authentication is enabled and the pretix version is vulnerable
  3. Inspect active OAuth applications
    Review the list of registered OAuth applications in the pretix admin panel under the OAuth provider section. Check for any third-party applications that users could be tricked into authorizing
    Affected if Any OAuth applications are registered in the system, particularly third-party apps

A user is affected if their pretix installation version is 1.16.0 through 4.15.0, 4.16.0, or 4.17.0 and OAuth functionality is enabled with registered applications.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 4.15.1 or later
Fixed in 4.15.1
Interim mitigation

Upgrade pretix to version 4.15.1, 4.16.1, or 4.17.1 to ensure proper session validation during OAuth authorization flows.

Recommended fix High confidence

4.17.1 (or 4.16.1 or 4.15.1 depending on your current major version branch)

  1. 1. Back up your pretix database and configuration files before starting the upgrade.
  2. 2. For pip-based installations: Run 'pip install --upgrade pretix' to upgrade to the latest version.
  3. 3. For Docker-based deployments: Pull the latest pretix Docker image (e.g., 'docker pull pretix/pretix:latest').
  4. 4. Run database migrations if required: 'pretix migrate' or through the management interface.
  5. 5. Restart all pretix worker processes and the web server.
  6. 6. Verify the upgrade by logging in and confirming OAuth authorization now requires an active authenticated session.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pretix Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-27891 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-27891 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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