Skip to main content
VulnerabilityPublished

CVE-2026-13603: pretix-oppwa · Improper Input Validation

Affects pretix-oppwaSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.0 Critical : upgrade to 1.4.4 as a priority.

Data as of 13 Nov 2026, 23:53 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 13 Nov 2026.

What to do

Upgrade pretix-oppwa to 1.4.4.

Affected software

ProductAffectedFixed in
pretixpretix-oppwaAffected
  • <1.4.4
Fixed in
  • 1.4.4
GitHubpretix-oppwapkg:github/pretix-oppwaOther threatsAffected
  • <1.4.4
Fixed in
  • 1.4.4

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

AI-suggested

Update pretix-oppwa to version 1.4.4 or later, which includes strict validation of the API URL to prevent malicious redirection. After applying the update, request a new access token from your payment provider and update it in the pretix configuration to invalidate any potentially leaked credentials. Patch status is not explicitly stated as 'official-fix' but the fix is included in version 1.4.4. No other mitigations are indicated.

Description

The payment integration pretix-oppwa provides support for the payment providers VR Payment, Hobex, and potentially others based on Oppwa's technology. The integration of Oppwa, following their official documentation, includes a step where the user is redirected from the payment provider back to our system with a query parameter like ?resourcePath=/v1/checkouts/{checkoutId}/payment in the URL. Our system is then supposed to fetch the status of the transaction from the URL given by baseUrl + resourcePath. Our plugin pretix-oppwa did so insecurely by concatenating the parameter form the URL to the base domain of the API without further validation and, critically, without a / at the end of the baseUrl. Therefore, an attacker could inject a resourcePath argument in a way that causes pretix to call a different server instead. Since the request includes the access token (API key) of the Oppwa account, this would leak the access token, giving access to data contained in the payment provider's system. This is fixed with the release today by strictly validating the given API URL. After installing the update, we recommend asking your payment provider for a new access token and updating it in pretix.

References

Community reviews

Loading reviews…