CVE-2026-48008 is a medium-severity (CVSS 6.5) CWE-862 vulnerability in shopware/platform. A fix is available for shopware/platform — see the affected versions and patch details below.
Shopware: Privilege Escalation via Sync API Integration Admin Flag Bypass
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-48008.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-48008 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 390,400 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
shopware/platform🐘shopware/platform🐘shopware/core🐘shopware/coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Summary
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) correctly blocks this, but the Sync API bypasses the controller-level check by writing directly through the DAL EntityWriter. The integration entity definition lacks WriteProtection, and the admin field has no field-level restriction flag.
OWASP: A01:2021 — Broken Access Control
Root Cause
IntegrationController::upsertIntegration() checks $source->isAdmin() before allowing the admin field to be set. However, SyncController::sync() routes writes through SyncService → EntityWriter, which only applies:
AclWriteValidator— checks entity-level ACL (integration:createis sufficient)EntityProtectionValidator— checksWriteProtectionon entity definitions, butIntegrationDefinitionhas none
The admin field in IntegrationDefinition is a plain BoolField with no WriteProtection or special flag. The Sync API writes it without restriction.
Vulnerable code path:
src/Core/Framework/Api/Controller/SyncController.php→SyncService→EntityWriter::upsert()- Missing protection:
src/Core/Framework/Integration/IntegrationDefinition.php—adminfield has noWriteProtection(Context::SYSTEM_SCOPE)
Working protection (bypassed):
src/Core/Framework/Integration/IntegrationController.php:46-56—isAdmin()check only applies to the dedicated controller endpoint
Impact
- Complete admin API access — the escalated integration has full read/write on every entity: users, customers, orders, system configuration, integrations, plugins
- PII exfiltration — read all customer records (names, emails, addresses, order history)
- Persistent backdoor — the admin integration survives password changes and user deactivation
Remediation
Add WriteProtection(Context::SYSTEM_SCOPE) to IntegrationDefinition, matching how UserDefinition and AclRoleDefinition are already protected:
// src/Core/Framework/Integration/IntegrationDefinition.php
(new BoolField('admin', 'admin'))
->addFlags(new WriteProtection(Context::SYSTEM_SCOPE)),
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | shopware/platform | ≥ 6.7.0.0&&< 6.7.10.1 | 6.7.10.1composer require shopware/platform:^6.7.10.1 |
| 🐘Packagist | shopware/platform | all versions | 6.6.10.18composer require shopware/platform:^6.6.10.18 |
| 🐘Packagist | shopware/core | ≥ 6.7.0.0&&< 6.7.10.1 | 6.7.10.1composer require shopware/core:^6.7.10.1 |
| 🐘Packagist | shopware/core | all versions | 6.6.10.18composer require shopware/core:^6.6.10.18 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for shopware/platform, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update shopware/platform to 6.7.10.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-48008 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2026-48008 in your dependencies?
Find it across Packagist, including transitive dependencies.