shopware/core security advisory

CVE-2026-48008: Shopware: Privilege Escalation via Sync API Integration Admin Flag Bypass

CVE-2026-48008 is a medium-severity privilege escalation vulnerability in the PHP package shopware/core (CVSS 6.5), published 17 July 2026. It is fixed in 6.6.10.18 and 6.7.10.1, one per release line; earlier versions on each line are affected. Exploiting it needs an admin-level account.

medium 6.5 published 2026-07-17

Affected versions: < 6.6.10.18
>= 6.7.0.0, < 6.7.10.1
Fixed in: 6.6.10.18, 6.7.10.1
Newest release: 6.7.16.0
Severity: Medium · CVSS 6.5
Type: Privilege escalation
CWE-862
Exploited in the wild: Not on the CISA KEV list
checked 2026-11-04

Is your shopware/core version affected?

Run composer show shopware/core in your project, then enter the version. We check it against this and every other known shopware/core advisory.

Who can exploit CVE-2026-48008

Access: A high-privilege account in the app, such as an admin.

CVSS vector (scored by GitHub): CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N

Your app is only exposed if it uses the affected part of shopware/core. The advisory below says which part that is. If you are not sure, upgrade anyway: it costs less than finding out.

How to fix CVE-2026-48008 in shopware/core

Find the installed version: composer show shopware/core. If you never required it yourself, composer why shopware/core shows which package pulls it in.
Update it: composer update shopware/core --with-all-dependencies. You need the fixed version for your release line (6.6.10.18 and 6.7.10.1).
If Composer will not go that high, your composer.json constraint is holding it back. Widen it (for example "shopware/core": "^6.7.10.1" if you can take that version), or upgrade the package that requires it.
Run composer audit. It reads the same advisory data and should no longer list CVE-2026-48008.
Commit composer.lock and deploy it. On the server, run composer install --no-dev from the lock file, not composer update.

If you cannot upgrade yet

General hardening for privilege escalation issues while the upgrade waits. None of it replaces the fix.

Remove accounts you do not need and review what each role can do.
Put the admin area behind a VPN, IP allow-list or extra login until you upgrade.
If your app does not use the affected feature, note that in your audit, but still plan the upgrade.

The CVE-2026-48008 advisory

Shopware is an open commerce platform. Prior to 6.6.10.18 and 6.7.10.1, a non-admin API user with integration:create ACL privilege can escalate to full administrator by creating an integration with admin: true through the Sync API POST /api/_action/sync; the regular integration endpoint POST /api/integration blocks this, but SyncController::sync() routes writes through SyncService to EntityWriter::upsert(), and src/Core/Framework/Integration/IntegrationDefinition.php lacks WriteProtection on the admin field. This issue is fixed in versions 6.6.10.18 and 6.7.10.1.

Description from the CVE record, published by GitHub (the CVE Numbering Authority), via the NVD entry for CVE-2026-48008. Advisory title: “Shopware: Privilege Escalation via Sync API Integration Admin Flag Bypass”.

References

GitHub advisory GHSA-gv8p-48fr-4fxg github.com
Fix commit 1e047f6 github.com
Fix commit db5adff github.com
Release v6.6.10.18 github.com
Release v6.7.10.1 github.com

Other shopware/core advisories

medium CVE-2026-48013: Shopware: SSRF in Media External-Link Endpoint Bypasses IP Validation 2026-06-04
medium CVE-2026-48015: Shopware: Stored XSS via SVG file upload — no SVG sanitization 2026-06-04
medium CVE-2026-48016: Shopware: Unauthorized Payment Trigger for Foreign Orders via /store-api/handle-payment 2026-06-04
medium CVE-2026-48014: Shopware: Admin API ACL Bypass in Order State Transition Endpoints 2026-06-04
medium CVE-2026-48012: Shopware SSO referer trust leading to an arbitrary redirect target 2026-06-04
low CVE-2026-48011: Shopware: Timing-attack on admin panel allowing enumeration of administrator usernames 2026-06-04

Need help patching or upgrading? Laskyr does PHP and Laravel security fixes and upgrades. Tell us what you run and we reply with a plan and a price.

Ask about a fix

Where this data comes from

Affected and fixed versions: the Packagist security advisories API (GitHub Advisory Database and FriendsOfPHP), the same data composer audit uses. Synced 2026-11-03.
Description, score, weakness and references: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Exploited-in-the-wild status: the CISA Known Exploited Vulnerabilities catalog, checked 2026-11-04.
Compiled by Daniel Lasek at Laskyr from the sources above. The summary, “who can exploit it”, “how to fix it” and hardening sections are our plain-English reading of the record and are generated from it. The quoted description is the record's own text. Spot an error? Tell us.