ZDF
Sign inSign up

Vulnerabilities

Security research · CVE-2026-48016

Unauthorized Payment Trigger for Foreign Orders via /store-api/handle-payment

Published May 19, 2026 · catalog updated May 20, 2026 · Unauthorized Payment Trigger for

Last checked Nov 2, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-48016. EPSS is 0.41%. Act only if a listed version of Unauthorized Payment Trigger for is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Unauthorized Payment Trigger for).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium4.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.41%
Remediation
Version ranges on file
Affected products
composer shopware/core · composer shopware/platform

## Summary The Shopware Store API endpoint contains an object-level authorization flaw that allows a low-privileged external user with a normal customer or guest context to trigger the payment flow for another user’s order by supplying a foreign . The affected functionality is the Store API payment initiation and retry flow. The root cause is that the endpoint forwards the user-controlled into the payment processing logic without verifying that the caller owns the referenced order or has passed the required guest-order authentication. As a result, payment attempts for foreign orders are accepted by the server, which can compromise the integrity of order and payment workflows. ## Description Shopware exposes to initiate or retry the payment flow for an already created order. Under the normal order access model, customers should only be able to view or act on their own orders, and guest users should only be able to access guest orders after completing additional verification such as , email address, and postal code. The Store API route follows this model: authenticated customers only see their own orders, and guest users are denied access unless guest-order authentication is performed. However, does not follow the same protection model. It only checks whether the supplied exists and then directly forwards it into the payment processing flow. As a result, an attacker who cannot read orders through the intended protected route can still trigger the payment retry or payment initiation logic for another customer’s order as long as they know a valid foreign order ID. Although is a UUID-based identifier and is not trivially guessable, it is used throughout storefront order flows such as checkout finish, account order pages, payment change flows, and download links. It is therefore a business object identifier, not a secret bearer token. The server must not treat knowledge of a valid as sufficient authorization and must instead verify that the caller is entitled to act on th

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • composer shopware/core<6.6.10.18
  • composer shopware/core>=6.7.0.0 <6.7.10.1
  • composer shopware/platform<6.6.10.18
  • composer shopware/platform>=6.7.0.0 <6.7.10.1

How to fix CVE-2026-48016

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-48016. EPSS is 0.41%. Act only if a listed version of Unauthorized Payment Trigger for is installed.

Which versions are affected?

Compare what you have installed with <6.6.10.18, >=6.7.0.0 <6.7.10.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.41%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Shopware security

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. May 19, 2026 · Maintainer security tabs

    Detected

    ## Summary The Shopware Store API endpoint contains an object-level authorization flaw that allows a low-privileged external user with a normal customer or guest context to trigger the payment flow for another user’s order by supplying a foreign . The affected functionality is the Store API payment initiation and retry flow. The root cause is that the endpoint forwards the user-controlled into the

  2. May 20, 2026 · Maintainer security tabs

    Updated

    ## Summary The Shopware Store API endpoint contains an object-level authorization flaw that allows a low-privileged external user with a normal customer or guest context to trigger the payment flow for another user’s order by supplying a foreign . The affected functionality is the Store API payment initiation and retry flow. The root cause is that the endpoint forwards the user-controlled into the

Sources

  • CVE.orgVulnerability recordCVE-2026-48016

    Official CVE identifier

    cve.org
  • Maintainer security tabsVendor advisoryGHSA-9v5m-39wh-5chq

    ## Summary The Shopware Store API endpoint contains an object-level authorization flaw that allows a low-privileged external user with a normal customer or guest context to trigger the payment flow for another user’s order by supplying a foreign . The affected functionality is the Store API payment initiation and retry flow. The root cause is that the endpoint forwards the user-controlled into the

    github.com
  • urlscan.ioThreat intelligenceCVE-2026-48016
    urlscan.io

References

Freshness

Last verified in this catalog Nov 2, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • urlscan.ioNov 2, 2026
  • CVE.orgNov 2, 2026
  • Maintainer security tabsNov 2, 2026