Vulnerability-Lookup

CVE-2026-13603 (GCVE-0-2026-13603)

Vulnerability from cvelistv5 – Published: 2026-07-01 13:18 – Updated: 2026-07-01 14:07

Title

SSRF with API key leak in pretix-oppwa

Summary

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.

Severity

9 (Critical)


                        
                          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

SSVC

Exploitation: none Automatable: yes Technical Impact: total

CISA Coordinator (v2.0.3)

CWE

CWE-20 - Improper input validation
CWE-918 - Server-Side request forgery (SSRF)

Assigner

rami.io

References

1 reference

URL	Tags
https://pretix.eu/about/en/blog/20260701-release-…	vendor-advisory

Impacted products

1 product

Vendor	Product	Version
pretix	pretix-oppwa	Affected: 0 , < 1.4.4 (python)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-13603",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "yes"
                  },
                  {
                    "Technical Impact": "total"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-07-01T14:07:27.700177Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-07-01T14:07:36.332Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "collectionURL": "https://pypi.python.org",
          "defaultStatus": "unaffected",
          "packageName": "pretix-oppwa",
          "product": "pretix-oppwa",
          "repo": "https://github.com/pretix/pretix-oppwa",
          "vendor": "pretix",
          "versions": [
            {
              "lessThan": "1.4.4",
              "status": "affected",
              "version": "0",
              "versionType": "python"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eThe payment integration \u003ccode\u003epretix-oppwa\u003c/code\u003e provides support \nfor the payment providers VR Payment, Hobex, and potentially others \nbased on Oppwa\u0027s 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 \u003ccode\u003e?resourcePath=/v1/checkouts/{checkoutId}/payment\u003c/code\u003e in the URL. Our system is then supposed to fetch the status of the transaction from the URL given by \u003ccode\u003ebaseUrl + resourcePath\u003c/code\u003e.\u003c/p\u003e\u003cp\u003eOur plugin \u003ccode\u003epretix-oppwa\u003c/code\u003e did so insecurely by \nconcatenating the parameter form the URL to the base domain of the API \nwithout further validation and, critically, without a \u003ccode\u003e/\u003c/code\u003e at the end of the \u003ccode\u003ebaseUrl\u003c/code\u003e. Therefore, an attacker could inject a \u003ccode\u003eresourcePath\u003c/code\u003e argument in a way that causes pretix to call a \u003cem\u003edifferent\u003c/em\u003e\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\u0027s system. This is fixed with the\n release today by strictly validating the given API URL.\u003c/p\u003e\u003cp\u003e\n\n\u003c/p\u003e\u003cp\u003e\u003cstrong\u003eAfter installing the update, we recommend asking your payment provider for a new access token and updating it in pretix.\u003c/strong\u003e\u003c/p\u003e"
            }
          ],
          "value": "The payment integration pretix-oppwa provides support \nfor the payment providers VR Payment, Hobex, and potentially others \nbased on Oppwa\u0027s 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\n\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\u0027s system. This is fixed with the\n release today by strictly validating the given API URL.\n\n\n\n\n\n\n\n\n\nAfter installing the update, we recommend asking your payment provider for a new access token and updating it in pretix."
        }
      ],
      "impacts": [
        {
          "capecId": "CAPEC-37",
          "descriptions": [
            {
              "lang": "en",
              "value": "CAPEC-37 Retrieve Embedded Sensitive Data"
            }
          ]
        },
        {
          "capecId": "CAPEC-664",
          "descriptions": [
            {
              "lang": "en",
              "value": "CAPEC-664 Server Side Request Forgery"
            }
          ]
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "Automatable": "NOT_DEFINED",
            "Recovery": "NOT_DEFINED",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 9,
            "baseSeverity": "CRITICAL",
            "exploitMaturity": "UNREPORTED",
            "privilegesRequired": "NONE",
            "providerUrgency": "NOT_DEFINED",
            "subAvailabilityImpact": "LOW",
            "subConfidentialityImpact": "HIGH",
            "subIntegrityImpact": "HIGH",
            "userInteraction": "NONE",
            "valueDensity": "NOT_DEFINED",
            "vectorString": "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",
            "vulnAvailabilityImpact": "LOW",
            "vulnConfidentialityImpact": "HIGH",
            "vulnIntegrityImpact": "HIGH",
            "vulnerabilityResponseEffort": "NOT_DEFINED"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-20",
              "description": "CWE-20 Improper input validation",
              "lang": "en",
              "type": "CWE"
            }
          ]
        },
        {
          "descriptions": [
            {
              "cweId": "CWE-918",
              "description": "CWE-918 Server-Side request forgery (SSRF)",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-07-01T13:18:09.434Z",
        "orgId": "655498c3-6ec5-4f0b-aea6-853b334d05a6",
        "shortName": "rami.io"
      },
      "references": [
        {
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://pretix.eu/about/en/blog/20260701-release-2026-5-3/"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cstrong\u003eAfter installing the update, we recommend asking your payment provider for a new access token and updating it in pretix.\u003c/strong\u003e\u003cdiv\u003e\u003cstrong\u003eAttack detection:\u003c/strong\u003e If you have access logs, you can search them for \u003ccode\u003eresourcePath=\u003c/code\u003e not followed by a \u003ccode\u003e/\u003c/code\u003e or encoded slash \u003ccode\u003e%2F\u003c/code\u003e.\u003cstrong\u003e\u003c/strong\u003e\u003c/div\u003e"
            }
          ],
          "value": "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."
        }
      ],
      "title": "SSRF with API key leak in pretix-oppwa",
      "workarounds": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cstrong\u003eWorkaround:\u003c/strong\u003e If you are unable to update pretix quickly, we still recommend to try installing the \u003ccode\u003epretix-oppwa\u003c/code\u003e\n plugin in the latest version. We have not tested it with every old \npretix release, but we expect it to be compatible with any version after\n 2025.1. Otherwise, we recommend to \u003cstrong\u003euninstall\u003c/strong\u003e the \u003ccode\u003epretix-oppwa\u003c/code\u003e plugin."
            }
          ],
          "value": "Workaround: If you are unable to update pretix quickly, we still recommend to try installing the pretix-oppwa\n plugin in the latest version. We have not tested it with every old \npretix release, but we expect it to be compatible with any version after\n 2025.1. Otherwise, we recommend to uninstall the pretix-oppwa plugin."
        }
      ],
      "x_generator": {
        "engine": "Vulnogram 1.0.2"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "655498c3-6ec5-4f0b-aea6-853b334d05a6",
    "assignerShortName": "rami.io",
    "cveId": "CVE-2026-13603",
    "datePublished": "2026-07-01T13:18:09.434Z",
    "dateReserved": "2026-06-29T08:26:51.607Z",
    "dateUpdated": "2026-07-01T14:07:36.332Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-13603",
      "date": "2026-07-02",
      "epss": "0.00253",
      "percentile": "0.1658"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2026-13603\",\"sourceIdentifier\":\"655498c3-6ec5-4f0b-aea6-853b334d05a6\",\"published\":\"2026-07-01T14:16:31.910\",\"lastModified\":\"2026-07-02T18:43:45.710\",\"vulnStatus\":\"Deferred\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"The payment integration pretix-oppwa provides support \\nfor the payment providers VR Payment, Hobex, and potentially others \\nbased on Oppwa\u0027s 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\\n\\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\u0027s system. This is fixed with the\\n release today by strictly validating the given API URL.\\n\\n\\n\\n\\n\\n\\n\\n\\n\\nAfter installing the update, we recommend asking your payment provider for a new access token and updating it in pretix.\"}],\"affected\":[{\"source\":\"655498c3-6ec5-4f0b-aea6-853b334d05a6\",\"affectedData\":[{\"vendor\":\"pretix\",\"product\":\"pretix-oppwa\",\"defaultStatus\":\"unaffected\",\"collectionURL\":\"https://pypi.python.org\",\"packageName\":\"pretix-oppwa\",\"repo\":\"https://github.com/pretix/pretix-oppwa\",\"versions\":[{\"version\":\"0\",\"lessThan\":\"1.4.4\",\"versionType\":\"python\",\"status\":\"affected\"}]}]}],\"metrics\":{\"cvssMetricV40\":[{\"source\":\"655498c3-6ec5-4f0b-aea6-853b334d05a6\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"4.0\",\"vectorString\":\"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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X\",\"baseScore\":9.0,\"baseSeverity\":\"CRITICAL\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"attackRequirements\":\"NONE\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"vulnConfidentialityImpact\":\"HIGH\",\"vulnIntegrityImpact\":\"HIGH\",\"vulnAvailabilityImpact\":\"LOW\",\"subConfidentialityImpact\":\"HIGH\",\"subIntegrityImpact\":\"HIGH\",\"subAvailabilityImpact\":\"LOW\",\"exploitMaturity\":\"UNREPORTED\",\"confidentialityRequirement\":\"NOT_DEFINED\",\"integrityRequirement\":\"NOT_DEFINED\",\"availabilityRequirement\":\"NOT_DEFINED\",\"modifiedAttackVector\":\"NOT_DEFINED\",\"modifiedAttackComplexity\":\"NOT_DEFINED\",\"modifiedAttackRequirements\":\"NOT_DEFINED\",\"modifiedPrivilegesRequired\":\"NOT_DEFINED\",\"modifiedUserInteraction\":\"NOT_DEFINED\",\"modifiedVulnConfidentialityImpact\":\"NOT_DEFINED\",\"modifiedVulnIntegrityImpact\":\"NOT_DEFINED\",\"modifiedVulnAvailabilityImpact\":\"NOT_DEFINED\",\"modifiedSubConfidentialityImpact\":\"NOT_DEFINED\",\"modifiedSubIntegrityImpact\":\"NOT_DEFINED\",\"modifiedSubAvailabilityImpact\":\"NOT_DEFINED\",\"Safety\":\"NOT_DEFINED\",\"Automatable\":\"NOT_DEFINED\",\"Recovery\":\"NOT_DEFINED\",\"valueDensity\":\"NOT_DEFINED\",\"vulnerabilityResponseEffort\":\"NOT_DEFINED\",\"providerUrgency\":\"NOT_DEFINED\"}}],\"ssvcV203\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"ssvcData\":{\"timestamp\":\"2026-07-01T14:07:27.700177Z\",\"id\":\"CVE-2026-13603\",\"options\":[{\"exploitation\":\"none\"},{\"automatable\":\"yes\"},{\"technicalImpact\":\"total\"}],\"role\":\"CISA Coordinator\",\"version\":\"2.0.3\"}}]},\"weaknesses\":[{\"source\":\"655498c3-6ec5-4f0b-aea6-853b334d05a6\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-20\"},{\"lang\":\"en\",\"value\":\"CWE-918\"}]}],\"references\":[{\"url\":\"https://pretix.eu/about/en/blog/20260701-release-2026-5-3/\",\"source\":\"655498c3-6ec5-4f0b-aea6-853b334d05a6\"}]}}",
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2026-13603\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"yes\"}, {\"Technical Impact\": \"total\"}], \"version\": \"2.0.3\", \"timestamp\": \"2026-07-01T14:07:27.700177Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2026-07-01T14:07:32.426Z\"}}], \"cna\": {\"title\": \"SSRF with API key leak in pretix-oppwa\", \"impacts\": [{\"capecId\": \"CAPEC-37\", \"descriptions\": [{\"lang\": \"en\", \"value\": \"CAPEC-37 Retrieve Embedded Sensitive Data\"}]}, {\"capecId\": \"CAPEC-664\", \"descriptions\": [{\"lang\": \"en\", \"value\": \"CAPEC-664 Server Side Request Forgery\"}]}], \"metrics\": [{\"format\": \"CVSS\", \"cvssV4_0\": {\"Safety\": \"NOT_DEFINED\", \"version\": \"4.0\", \"Recovery\": \"NOT_DEFINED\", \"baseScore\": 9, \"Automatable\": \"NOT_DEFINED\", \"attackVector\": \"NETWORK\", \"baseSeverity\": \"CRITICAL\", \"valueDensity\": \"NOT_DEFINED\", \"vectorString\": \"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\", \"exploitMaturity\": \"UNREPORTED\", \"providerUrgency\": \"NOT_DEFINED\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"LOW\", \"attackRequirements\": \"NONE\", \"privilegesRequired\": \"NONE\", \"subIntegrityImpact\": \"HIGH\", \"vulnIntegrityImpact\": \"HIGH\", \"subAvailabilityImpact\": \"LOW\", \"vulnAvailabilityImpact\": \"LOW\", \"subConfidentialityImpact\": \"HIGH\", \"vulnConfidentialityImpact\": \"HIGH\", \"vulnerabilityResponseEffort\": \"NOT_DEFINED\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"GENERAL\"}]}], \"affected\": [{\"repo\": \"https://github.com/pretix/pretix-oppwa\", \"vendor\": \"pretix\", \"product\": \"pretix-oppwa\", \"versions\": [{\"status\": \"affected\", \"version\": \"0\", \"lessThan\": \"1.4.4\", \"versionType\": \"python\"}], \"packageName\": \"pretix-oppwa\", \"collectionURL\": \"https://pypi.python.org\", \"defaultStatus\": \"unaffected\"}], \"solutions\": [{\"lang\": \"en\", \"value\": \"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.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"\u003cstrong\u003eAfter installing the update, we recommend asking your payment provider for a new access token and updating it in pretix.\u003c/strong\u003e\u003cdiv\u003e\u003cstrong\u003eAttack detection:\u003c/strong\u003e If you have access logs, you can search them for \u003ccode\u003eresourcePath=\u003c/code\u003e not followed by a \u003ccode\u003e/\u003c/code\u003e or encoded slash \u003ccode\u003e%2F\u003c/code\u003e.\u003cstrong\u003e\u003c/strong\u003e\u003c/div\u003e\", \"base64\": false}]}], \"references\": [{\"url\": \"https://pretix.eu/about/en/blog/20260701-release-2026-5-3/\", \"tags\": [\"vendor-advisory\"]}], \"workarounds\": [{\"lang\": \"en\", \"value\": \"Workaround: If you are unable to update pretix quickly, we still recommend to try installing the pretix-oppwa\\n plugin in the latest version. We have not tested it with every old \\npretix release, but we expect it to be compatible with any version after\\n 2025.1. Otherwise, we recommend to uninstall the pretix-oppwa plugin.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"\u003cstrong\u003eWorkaround:\u003c/strong\u003e If you are unable to update pretix quickly, we still recommend to try installing the \u003ccode\u003epretix-oppwa\u003c/code\u003e\\n plugin in the latest version. We have not tested it with every old \\npretix release, but we expect it to be compatible with any version after\\n 2025.1. Otherwise, we recommend to \u003cstrong\u003euninstall\u003c/strong\u003e the \u003ccode\u003epretix-oppwa\u003c/code\u003e plugin.\", \"base64\": false}]}], \"x_generator\": {\"engine\": \"Vulnogram 1.0.2\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"The payment integration pretix-oppwa provides support \\nfor the payment providers VR Payment, Hobex, and potentially others \\nbased on Oppwa\u0027s 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\\n\\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\u0027s system. This is fixed with the\\n release today by strictly validating the given API URL.\\n\\n\\n\\n\\n\\n\\n\\n\\n\\nAfter installing the update, we recommend asking your payment provider for a new access token and updating it in pretix.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"\u003cp\u003eThe payment integration \u003ccode\u003epretix-oppwa\u003c/code\u003e provides support \\nfor the payment providers VR Payment, Hobex, and potentially others \\nbased on Oppwa\u0027s 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 \u003ccode\u003e?resourcePath=/v1/checkouts/{checkoutId}/payment\u003c/code\u003e in the URL. Our system is then supposed to fetch the status of the transaction from the URL given by \u003ccode\u003ebaseUrl + resourcePath\u003c/code\u003e.\u003c/p\u003e\u003cp\u003eOur plugin \u003ccode\u003epretix-oppwa\u003c/code\u003e did so insecurely by \\nconcatenating the parameter form the URL to the base domain of the API \\nwithout further validation and, critically, without a \u003ccode\u003e/\u003c/code\u003e at the end of the \u003ccode\u003ebaseUrl\u003c/code\u003e. Therefore, an attacker could inject a \u003ccode\u003eresourcePath\u003c/code\u003e argument in a way that causes pretix to call a \u003cem\u003edifferent\u003c/em\u003e\\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\u0027s system. This is fixed with the\\n release today by strictly validating the given API URL.\u003c/p\u003e\u003cp\u003e\\n\\n\u003c/p\u003e\u003cp\u003e\u003cstrong\u003eAfter installing the update, we recommend asking your payment provider for a new access token and updating it in pretix.\u003c/strong\u003e\u003c/p\u003e\", \"base64\": false}]}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-20\", \"description\": \"CWE-20 Improper input validation\"}]}, {\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-918\", \"description\": \"CWE-918 Server-Side request forgery (SSRF)\"}]}], \"providerMetadata\": {\"orgId\": \"655498c3-6ec5-4f0b-aea6-853b334d05a6\", \"shortName\": \"rami.io\", \"dateUpdated\": \"2026-07-01T13:18:09.434Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2026-13603\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-07-01T14:07:36.332Z\", \"dateReserved\": \"2026-06-29T08:26:51.607Z\", \"assignerOrgId\": \"655498c3-6ec5-4f0b-aea6-853b334d05a6\", \"datePublished\": \"2026-07-01T13:18:09.434Z\", \"assignerShortName\": \"rami.io\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}

FKIE_CVE-2026-13603

Vulnerability from fkie_nvd - Published: 2026-07-01 14:16 - Updated: 2026-07-02 18:43

Severity

9.0 (Critical) - 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

Summary

References

	URL	Tags
	655498c3-6ec5-4f0b-aea6-853b334d05a6	https://pretix.eu/about/en/blog/20260701-release-2026-5-3/

Impacted products

	Vendor	Product	Version

JSON

To clipboard

{
  "affected": [
    {
      "affectedData": [
        {
          "collectionURL": "https://pypi.python.org",
          "defaultStatus": "unaffected",
          "packageName": "pretix-oppwa",
          "product": "pretix-oppwa",
          "repo": "https://github.com/pretix/pretix-oppwa",
          "vendor": "pretix",
          "versions": [
            {
              "lessThan": "1.4.4",
              "status": "affected",
              "version": "0",
              "versionType": "python"
            }
          ]
        }
      ],
      "source": "655498c3-6ec5-4f0b-aea6-853b334d05a6"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "The payment integration pretix-oppwa provides support \nfor the payment providers VR Payment, Hobex, and potentially others \nbased on Oppwa\u0027s 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\n\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\u0027s system. This is fixed with the\n release today by strictly validating the given API URL.\n\n\n\n\n\n\n\n\n\nAfter installing the update, we recommend asking your payment provider for a new access token and updating it in pretix."
    }
  ],
  "id": "CVE-2026-13603",
  "lastModified": "2026-07-02T18:43:45.710",
  "metrics": {
    "cvssMetricV40": [
      {
        "cvssData": {
          "Automatable": "NOT_DEFINED",
          "Recovery": "NOT_DEFINED",
          "Safety": "NOT_DEFINED",
          "attackComplexity": "LOW",
          "attackRequirements": "NONE",
          "attackVector": "NETWORK",
          "availabilityRequirement": "NOT_DEFINED",
          "baseScore": 9.0,
          "baseSeverity": "CRITICAL",
          "confidentialityRequirement": "NOT_DEFINED",
          "exploitMaturity": "UNREPORTED",
          "integrityRequirement": "NOT_DEFINED",
          "modifiedAttackComplexity": "NOT_DEFINED",
          "modifiedAttackRequirements": "NOT_DEFINED",
          "modifiedAttackVector": "NOT_DEFINED",
          "modifiedPrivilegesRequired": "NOT_DEFINED",
          "modifiedSubAvailabilityImpact": "NOT_DEFINED",
          "modifiedSubConfidentialityImpact": "NOT_DEFINED",
          "modifiedSubIntegrityImpact": "NOT_DEFINED",
          "modifiedUserInteraction": "NOT_DEFINED",
          "modifiedVulnAvailabilityImpact": "NOT_DEFINED",
          "modifiedVulnConfidentialityImpact": "NOT_DEFINED",
          "modifiedVulnIntegrityImpact": "NOT_DEFINED",
          "privilegesRequired": "NONE",
          "providerUrgency": "NOT_DEFINED",
          "subAvailabilityImpact": "LOW",
          "subConfidentialityImpact": "HIGH",
          "subIntegrityImpact": "HIGH",
          "userInteraction": "NONE",
          "valueDensity": "NOT_DEFINED",
          "vectorString": "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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
          "version": "4.0",
          "vulnAvailabilityImpact": "LOW",
          "vulnConfidentialityImpact": "HIGH",
          "vulnIntegrityImpact": "HIGH",
          "vulnerabilityResponseEffort": "NOT_DEFINED"
        },
        "source": "655498c3-6ec5-4f0b-aea6-853b334d05a6",
        "type": "Secondary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2026-13603",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "yes"
            },
            {
              "technicalImpact": "total"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2026-07-01T14:07:27.700177Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2026-07-01T14:16:31.910",
  "references": [
    {
      "source": "655498c3-6ec5-4f0b-aea6-853b334d05a6",
      "url": "https://pretix.eu/about/en/blog/20260701-release-2026-5-3/"
    }
  ],
  "sourceIdentifier": "655498c3-6ec5-4f0b-aea6-853b334d05a6",
  "vulnStatus": "Deferred",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-20"
        },
        {
          "lang": "en",
          "value": "CWE-918"
        }
      ],
      "source": "655498c3-6ec5-4f0b-aea6-853b334d05a6",
      "type": "Secondary"
    }
  ]
}

GHSA-29FQ-JC8M-8RQ2

Vulnerability from github – Published: 2026-07-01 15:35 – Updated: 2026-07-01 15:35

Details

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.

Severity

9.0 (Critical)


                  
                    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

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-13603"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-20"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-07-01T14:16:31Z",
    "severity": "CRITICAL"
  },
  "details": "The payment integration pretix-oppwa provides support \nfor the payment providers VR Payment, Hobex, and potentially others \nbased on Oppwa\u0027s 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\n\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\u0027s system. This is fixed with the\n release today by strictly validating the given API URL.\n\n\n\n\n\n\n\n\n\nAfter installing the update, we recommend asking your payment provider for a new access token and updating it in pretix.",
  "id": "GHSA-29fq-jc8m-8rq2",
  "modified": "2026-07-01T15:35:18Z",
  "published": "2026-07-01T15:35:18Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-13603"
    },
    {
      "type": "WEB",
      "url": "https://pretix.eu/about/en/blog/20260701-release-2026-5-3"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
      "type": "CVSS_V4"
    }
  ]
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Detection rules are retrieved from Rulezet.

Action not permitted

CVE-2026-13603 (GCVE-0-2026-13603)

FKIE_CVE-2026-13603

GHSA-29FQ-JC8M-8RQ2

Tags

Sightings

Nomenclature