shopware/platform
Affected
- introduced
6.7.0.0, fixed6.7.10.1(ecosystem)
Fixed versions
6.7.10.1
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-48008
Shopware: Privilege Escalation via Sync API Integration Admin Flag Bypass
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:create is sufficient)EntityProtectionValidator — checks WriteProtection on entity definitions, but IntegrationDefinition has noneThe 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()src/Core/Framework/Integration/IntegrationDefinition.php — admin field has no WriteProtection(Context::SYSTEM_SCOPE)Working protection (bypassed):
src/Core/Framework/Integration/IntegrationController.php:46-56 — isAdmin() check only applies to the dedicated controller endpointImpact
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)),Medium Basis: The source's own band: MODERATE
6.7.0.0, fixed 6.7.10.1 (ecosystem)6.7.10.1
The export has no generic command for this ecosystem.
0, fixed 6.6.10.18 (ecosystem)6.6.10.18
The export has no generic command for this ecosystem.
6.7.0.0, fixed 6.7.10.1 (ecosystem)6.7.10.1
The export has no generic command for this ecosystem.
0, fixed 6.6.10.18 (ecosystem)6.6.10.18
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0