{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-13603 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-13603 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-13603 is a critical server-side request forgery vulnerability in pretix-oppwa, published on 1 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-13603 and fix it if it is affected.\n\nWhat it is: CVE-2026-13603 is a critical server-side request forgery vulnerability in pretix-oppwa, published on 1 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-13603 in the wild and no public exploit code.\n\nAffected product: pretix-oppwa. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-13603/ (Markdown: https://insights.sbomify.com/CVE-2026-13603/index.md)","id":"CVE-2026-13603","markdown":"https://insights.sbomify.com/CVE-2026-13603/index.md","name":"CVE-2026-13603","record":{"aliases":["GHSA-29fq-jc8m-8rq2"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"pretix payment plugin","requires_auth":"none","summary":"Attackers can exploit improper URL validation to force server-side requests to arbitrary hosts, leaking API keys and accessing payment provider data.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"rami.io","cpe":[],"cvss":{"score":9,"severity":"critical","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"The payment integration pretix-oppwa provides support \nfor the payment providers VR Payment, Hobex, and potentially others \nbased on Oppwa's technology. The integration of Oppwa, following their \nofficial documentation, includes a step where the user is redirected \nfrom the payment provider back to our system with a query parameter like\n ?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.\n\nOur plugin pretix-oppwa did so insecurely by \nconcatenating the parameter form the URL to the base domain of the API \nwithout 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\n server instead. Since the request includes the access token (API key) \nof the Oppwa account, this would leak the access token, giving access to\n data contained in the payment provider's system. This is fixed with the\n release today by strictly validating the given API URL.\n\nAfter installing the update, we recommend asking your payment provider for a new access token and updating it in pretix.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"SSRF with API key leak in pretix-oppwa","id":"CVE-2026-13603","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Pixelavo \u003c 1.5.4 - Unauthenticated Facebook CAPI Event Injection via pixelavo_event AJAX","id":"CVE-2026-13604"},"packages":[],"prev":{"headline":"Session takeover vulnerability","id":"CVE-2026-13602"},"products":["pretix-oppwa"],"published":"2026-07-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-01","vendors":["pretix"]},"summary":"Attackers can exploit improper URL validation to force server-side requests to arbitrary hosts, leaking API keys and accessing payment provider data.","url":"https://insights.sbomify.com/CVE-2026-13603/"}