CVE-2026-48016

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 4.3 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:github_m, epss
4.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Shopware is an open commerce platform. Prior to 6.6.10.18 and 6.7.10.1, the Store API endpoint /store-api/handle-payment in src/Core/Checkout/Payment/SalesChannel/HandlePaymentMethodRoute.php accepts a user-controlled orderId and forwards it to src/Core/Checkout/Payment/PaymentProcessor.php without verifying order ownership or guest-order authentication, allowing a normal customer or guest context to trigger the payment flow for another user's order while /store-api/order enforces the expected ownership model. This issue is fixed in versions 6.6.10.18 and 6.7.10.1.

CVSS v3
4.3
EG Score
4.3(low)
EG Risk
—
EPSS
14.9%
KEV
Not listed

Published

June 4, 2026

Last Modified

July 20, 2026

Advisory Details (5)

Auto-updated Jul 17, 2026
Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

Security Release v6.7.10.1

Patch available: shopware/shopware v6.7.10.1

https://github.com/shopware/shopware/releases/tag/v6.7.10.1
github_release Patch Available

Security Release v6.6.10.18

Patch available: shopware/shopware v6.6.10.18

https://github.com/shopware/shopware/releases/tag/v6.6.10.18
github_commit

commit df15f2e607dc (shopware/shopware)

Fix landed in shopware/shopware commit df15f2e607dc — awaiting tagged release

https://github.com/shopware/shopware/commit/df15f2e607dcf9ebc4a26ec622ffcf452dc25090
github_commit

commit 69dd5b6cb01d (shopware/shopware)

Fix landed in shopware/shopware commit 69dd5b6cb01d — awaiting tagged release

https://github.com/shopware/shopware/commit/69dd5b6cb01d3c2aea49ac29dd4512a87836ac3f
github Patch Available

Unauthorized Payment Trigger for Foreign Orders via /store-api/handle-payment · Advisory · shopware/shopware · GitHub

https://github.com/shopware/shopware/security/advisories/GHSA-9v5m-39wh-5chq

Vendor Advisories for CVE-2026-48016(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 1 ecosystem)
Packagist(2)
PackageVulnerable rangeFixed inDependents
shopware/core6.3.0.0 ... v6.6.9.0 (166 versions)6.6.10.18—
shopware/platform6.3.0.0 ... v6.6.9.0 (166 versions)6.6.10.18—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 5× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:24 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 02:29 UTCEPSS rescore
  6. 2026-06-14 23:18 UTCEPSS rescore
  7. 2026-06-13 23:00 UTCEPSS rescore
  8. 2026-06-12 23:12 UTCEPSS rescore
  9. 2026-06-04 20:10 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-48016?
CVE-2026-48016 is a medium vulnerability published on June 4, 2026. Shopware is an open commerce platform. Prior to 6.6.10.18 and 6.7.10.1, the Store API endpoint /store-api/handle-payment in src/Core/Checkout/Payment/SalesChannel/HandlePaymentMethodRoute.php accepts a user-controlled orderId and forwards it to src/Core/Checkout/Payment/PaymentProcessor.php without…
When was CVE-2026-48016 disclosed?
CVE-2026-48016 was first published in the National Vulnerability Database on June 4, 2026, with the most recent update on July 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48016 actively exploited?
CVE-2026-48016 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 14.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-48016?
CVE-2026-48016 has a CVSS v3 base score of 4.3 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-48016?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48016, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48016

Explore →

Is Your Infrastructure Affected by CVE-2026-48016?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs