How severe is GHSA-gv8p-48fr-4fxg?

GHSA-gv8p-48fr-4fxg has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-gv8p-48fr-4fxg?

GHSA-gv8p-48fr-4fxg affects the following packages: shopware/platform (Packagist), shopware/platform (Packagist), shopware/core (Packagist), shopware/core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-gv8p-48fr-4fxg?

Update shopware/platform to 6.7.10.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gv8p-48fr-4fxg is resolved across your whole dependency graph.

How do I detect GHSA-gv8p-48fr-4fxg in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for shopware/platform. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-gv8p-48fr-4fxg if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-gv8p-48fr-4fxg?

O3 pinpoints whether GHSA-gv8p-48fr-4fxg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-gv8p-48fr-4fxg actively exploited in the wild?

No public exploit code has been indexed for GHSA-gv8p-48fr-4fxg yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-gv8p-48fr-4fxg?

GHSA-gv8p-48fr-4fxg is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-gv8p-48fr-4fxg published, and has it been updated?

GHSA-gv8p-48fr-4fxg was published on June 4, 2026 and was last updated on June 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-gv8p-48fr-4fxg

MEDIUM

Shopware: Privilege Escalation via Sync API Integration Admin Flag Bypass

Also known asCVE-2026-48008

Published

Jun 4, 2026

Updated

Jun 4, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Blast Radius

4 pkgs affected

🐘shopware/platform🐘shopware/platform🐘shopware/core🐘shopware/core

Real-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:create is sufficient)
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

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

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`shopware/platform`	≥ 6.7.0.0&&< 6.7.10.1	6.7.10.1
🐘Packagist	`shopware/platform`	all versions	6.6.10.18
🐘Packagist	`shopware/core`	≥ 6.7.0.0&&< 6.7.10.1	6.7.10.1
🐘Packagist	`shopware/core`	all versions	6.6.10.18

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for shopware/platform. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 GHSA-gv8p-48fr-4fxg is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-gv8p-48fr-4fxg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-gv8p-48fr-4fxg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## 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::upsertI

O3 Security · Impact-Aware SCA

Is GHSA-gv8p-48fr-4fxg in your dependencies?

O3 detects GHSA-gv8p-48fr-4fxg across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works