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 constructs a URL by concatenating the resourcePath value supplied by the Oppwa payment provider with a configured base API URL without validating the path or restricting the domain. Because the redirect URL can be influenced by an attacker, a crafted resourcePath can point to an arbitrary host. The resulting server‑side request includes the Oppwa API access token that the plugin transmits in the outgoing request, causing a Server‑Side Request Forgery that not only allows arbitrary HTTP calls but also leaks credentials. This gives the attacker read access to transaction data in the payment provider’s system, representing a critical privacy breach and potential entry point for further compromise. The vulnerability is a classic example of Improper Input Validation (CWE‑20) and represents an SSRF flaw (CWE‑918). The plugin did not enforce a leading slash or domain check, which allowed the attacker to subvert the intended API endpoint. Successful exploitation would expose the Oppwa access token and any payment data retrievable through that token, effectively bypassing any client‑side authentication mechanisms and enabling the attacker to read or potentially modify payment information.

Affected Systems

All sites running the pretix-oppwa plugin before the 2026‑5‑3 release are affected. The vulnerable logic existed in every earlier release of the plugin for the pretix e‑commerce platform, and the 2026‑5‑3 update replaces the insecure concatenation with strict URL validation.

Risk and Exploitability

The flaw has a CVSS score of 9, indicating critical severity, and an EPSS score of less than 1 %, showing a low but non‑zero likelihood of exploitation in the wild. It is not listed in CISA’s KEV catalog currently. The attack vector requires an attacker able to influence the redirect URL that the payment provider sends back to pretix; by supplying a crafted resourcePath, the attacker can force pretix to perform a server‑side request to an arbitrary host and leak the Oppwa API token. Successful exploitation would grant read access to payment transaction data in the provider’s system.

Generated by OpenCVE AI on July 22, 2026 at 14:31 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 pretix‑oppwa update, which fixes the input validation flaw (CWE‑20) and the SSRF vulnerability (CWE‑918), then rotate the Oppwa API key.
  • If you cannot upgrade immediately, install the latest pretix‑oppwa version that includes the fix; if it is incompatible, remove the plugin until a patched version is available.
  • Limit outgoing requests from your pretix server to the official Oppwa API domain (e.g., www.oppwa.com) using firewall rules or network segmentation to block unintended SSRF calls.

Generated by OpenCVE AI on July 22, 2026 at 14:31 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

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-22T14:45:03Z

Weaknesses
  • CWE-20

    Improper Input Validation

  • CWE-918

    Server-Side Request Forgery (SSRF)