# Shopware: Timing-attack on admin panel allowing enumeration of administrator usernames Advisory record · `GHSA-7w52-7jvm-m9vw` - **Identifiers:** `GHSA-7w52-7jvm-m9vw` · `CVE-2026-48011` · `PKSA-xwkj-rryn-xz6v` · `PKSA-yt77-qm1k-2vvb` - **State:** Confirmed - **Severity:** CVSS 3.7 Low - **Critical:** No - **Weakness (CWE):** [CWE-208](https://cwe.mitre.org/data/definitions/208.html) - **Tags:** [CWE-208](https://agentprime.io/advisories/tag/cwe-208.md) - **Published:** 4 Jun 2026 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 4 Jun 2026, 19:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `shopware/platform` (Packagist): affected `>=6.7.0.0, <6.7.10.1 || <6.6.10.18`; fixed in `6.7.10.1`, `6.6.10.18` - `shopware/core` (Packagist): affected `>=6.7.0.0, <6.7.10.1 || <6.6.10.18`; fixed in `6.7.10.1`, `6.6.10.18` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Shopware's shopware/platform and shopware/core Packagist packages are affected in versions below 6.6.10.18 and from 6.7.0.0 up to but not including 6.7.10.1. The OAuth token endpoint returns early for usernames that do not exist and only runs password verification for existing users, so response timing can reveal which administrator usernames exist. An attacker with network access to the token endpoint could use this timing difference to enumerate usernames, which could then support targeted password guessing or credential stuffing. Upgrade to 6.6.10.18, or 6.7.10.1 for the 6.7 line. Written 31 Oct 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 3.7 Low, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0022, the 12th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:01 UTC: First seen by agentprime - 31 Oct 2026, 14:01 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-7w52-7jvm-m9vw) ## Sources - [GitHub Advisory Database: GHSA-7w52-7jvm-m9vw](https://github.com/advisories/GHSA-7w52-7jvm-m9vw) - [OSV: GHSA-7w52-7jvm-m9vw](https://osv.dev/vulnerability/GHSA-7w52-7jvm-m9vw) - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .