CVE-2026-48008

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:

1. AclWriteValidator, checks entity-level ACL (integration:create is sufficient)
2. EntityProtectionValidator, checks WriteProtection on entity definitions, but IntegrationDefinition has 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, 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 endpoint

• 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

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

CVE-2026-48008 has a CVSS score of 6.5 (Medium). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (6.7.10.1, 6.6.10.18); upgrading removes the vulnerable code path.

Kodem intelligence

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)),

1. What is CVE-2026-48008? CVE-2026-48008 is a medium-severity missing authorization vulnerability in shopware/platform (composer), affecting versions >= 6.7.0.0, < 6.7.10.1. It is fixed in 6.7.10.1, 6.6.10.18. The application does not perform an authorization check before performing a sensitive operation.
2. How severe is CVE-2026-48008? CVE-2026-48008 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2026-48008?
   • shopware/platform (composer) (versions >= 6.7.0.0, < 6.7.10.1)
   • shopware/core (composer) (versions >= 6.7.0.0, < 6.7.10.1)
4. Is there a fix for CVE-2026-48008? Yes. CVE-2026-48008 is fixed in 6.7.10.1, 6.6.10.18. Upgrade to this version or later.
5. Is CVE-2026-48008 exploitable, and should I be worried? Whether CVE-2026-48008 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-48008 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-48008?
   • Upgrade shopware/platform to 6.7.10.1 or later
   • Upgrade shopware/platform to 6.6.10.18 or later
   • Upgrade shopware/core to 6.7.10.1 or later
   • Upgrade shopware/core to 6.6.10.18 or later