Categories
CVE-2026-48011 low CVSS 3.7

Vulnerability in shopware/platform (CVE-2026-48011)

Summary

Vulnerability in shopware/platform (CVE-2026-48011). Risk of unauthorized operations or information disclosure. Exploitable via password_verify. Mitigation: upgrade to 6.6.10.18 or later.

Original description

The description as published by the source.

Summary

There is a Proof of Concept which is able to enumerate the usernames of administrator users. This was possible by performing a timing attack.

Details

The faulty code exists in src/Core/Framework/Api/OAuth/UserRepository.php:

public function getUserEntityByUserCredentials(
        string $username,
        #[\SensitiveParameter]
        string $password,
        string $grantType,
        ClientEntityInterface $clientEntity
    ): ?UserEntityInterface {
        if ($this->loginConfigService->getConfig()?->useDefault === false) {
            // never allow login via password if the default login is disabled (e.g. using SSO only)
            return null;
        }

        $builder = $this->connection->createQueryBuilder();
        $user = $builder->select('user.id', 'user.password')
            ->from('user')
            ->where('username = :username')
            ->setParameter('username', $username)
            ->fetchAssociative();

        // PATH 1: EARLY RETURN WHEN USERNAME IS NOT FOUND
        if (!$user) {
            return null;
        }

        // PATH 2: VERIFY PASSWORD IF USER IS FOUND
        if (!password_verify($password, (string) $user['password'])) {
            return null;
        }

        return new User(Uuid::fromBytesToHex($user['id']));
    }

Subroutine getUserEntityByUserCredentials() is called when an auth request is sen…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-48011 has been found in shopware/platform.
Attackers can target a specific entry point like password_verify over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.7/10.
What to do: upgrade shopware/platform to 6.6.10.18 or later.
If unsure, ask your IT team or search "shopware/platform CVE-2026-48011" on the vendor's site.

CVE-2026-48011 (shopware/platform) — CWE-208 / CVSS v3 3.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: password_verify
Patched: 6.6.10.18 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-208) exists in shopware/platform. Attackers reach the vulnerable code path via password_verify without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of shopware/platform. Attack surface: password_verify.

🔥 Severity

Severity: Low (CVSS 3.7/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 6.6.10.18.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'shopware/platform' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'shopware/platform' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で shopware/platform を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade shopware/platform to 6.6.10.18

    ステージング環境で 6.6.10.18 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

composer shopware/platform
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.10.18"}]}]
composer shopware/core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.10.18"}]}]
Packagist shopware/platform
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.10.18"}]}]
Packagist shopware/core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.10.18"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details