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.
Published: 2026-07-01
Score: 9 Critical
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The pretix‑oppwa plugin builds a request URL by concatenating a resourcePath value supplied by the payment provider with a configured base API URL. It does this without validating the path or enforcing a trailing slash, which allows a malicious attacker to supply a resourcePath that points to any host. This flaw results in a server‑side request to an unintended destination while the request still carries the Oppwa API access token embedded by the plugin, leaking the credential and exposing all payment data retrievable through that token. The vulnerability is an example of Improper Input Validation and a classic SSRF flaw, providing read access to transaction data and potentially enabling further compromise.

Affected Systems

All pretix installations that use the pretix‑oppwa plugin and that have not applied the 2026‑5‑3 update are affected. The issue exists in every previous release of the plugin for the pretix e‑commerce platform. Versions predating the 2026‑5‑3 release, regardless of the pretix core version, are vulnerable.

Risk and Exploitability

The flaw carries a CVSS score of 9, indicating critical severity, and an EPSS score of less than 1 %, indicating a low but non-zero likelihood of exploitation in the wild. It is not listed in CISA’s KEV catalog. Based on the description, it is inferred that the attack vector requires an attacker capable of influencing the redirect URL that the payment provider sends back to pretix; by tampering with the resourcePath query parameter, the attacker can force pretix to perform an arbitrary outbound request, retrieving the embedded API token. If exploited, the attacker gains read access to the payment provider’s system and any data obtainable through the compromised token.

Generated by OpenCVE AI on August 1, 2026 at 23:41 UTC.

Remediation

Vendor Solution

After installing the update, we recommend asking your payment provider for a new access token and updating it in pretix.Attack detection: If you have access logs, you can search them for resourcePath= not followed by a / or encoded slash %2F.


Vendor Workaround

Workaround: If you are unable to update pretix quickly, we still recommend to try installing the pretix-oppwa plugin in the latest version. We have not tested it with every old pretix release, but we expect it to be compatible with any version after 2025.1. Otherwise, we recommend to uninstall the pretix-oppwa plugin.


OpenCVE Recommended Actions

  • Deploy the 2026‑5‑3 update for pretix‑oppwa, which validates the resourcePath and eliminates the SSRF flaw, then rotate the Oppwa API key.
  • If an immediate update is not possible, install the latest pretix‑oppwa release that contains the fix; if the patched version is incompatible with your pretix core, temporarily remove the plugin until a compatible update is available.
  • Configure network rules or host‑based firewall restrictions to allow outbound requests from the pretix server only to the official Oppwa API domain (e.g., www.oppwa.com), thereby blocking unintended SSRF calls.

Generated by OpenCVE AI on August 1, 2026 at 23:41 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 01 Jul 2026 18:00:00 +0000

Type Values Removed Values Added
First Time appeared Pretix
Pretix pretix-oppwa
Vendors & Products Pretix
Pretix pretix-oppwa

Wed, 01 Jul 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Wed, 01 Jul 2026 13:45:00 +0000

Type Values Removed Values Added
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.
Title SSRF with API key leak in pretix-oppwa
Weaknesses CWE-20
CWE-918
References
Metrics cvssV4_0

{'score': 9, 'vector': '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'}


Subscriptions

Pretix Pretix-oppwa
cve-icon MITRE

Status: PUBLISHED

Assigner: rami.io

Published:

Updated: 2026-07-01T14:07:36.332Z

Reserved: 2026-06-29T08:26:51.607Z

Link: CVE-2026-13603

cve-icon Vulnrichment

Updated: 2026-07-01T14:07:32.426Z

cve-icon NVD

Status : Deferred

Published: 2026-07-01T14:16:31.910

Modified: 2026-07-02T18:43:45.710

Link: CVE-2026-13603

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-01T23:45:03Z

Weaknesses
  • CWE-20

    Improper Input Validation

  • CWE-918

    Server-Side Request Forgery (SSRF)