CVE-2026-48009 — shopware / platform
Exposure of Sensitive Information to an Unauthorized ActorSummary
A low-privilege admin user with user_recovery:read ACL can take over any admin account. The attacker triggers password recovery for the victim (unauthenticated endpoint), reads the recovery hash from the Admin API search endpoint, then uses the hash to reset the victim's password (another unauthenticated endpoint). The recovery hash — intended to be secret and delivered only via email — is fully readable through the standard entity search API.
OWASP: A01:2021 — Broken Access Control
Root Cause
The user_recovery entity exposes its hash field through the Admin API search endpoint (POST /api/search/user-recovery). The hash field lacks ApiAware(false) or ReadProtection, so any user with user_recovery:read ACL can read it.
The password recovery flow assumes the hash is delivered exclusively via email. The Admin API provides an alternative channel to obtain it, breaking this assumption.
Three endpoints combine to form the attack:
POST /api/_action/user/user-recovery— triggers recovery, creates hash in DB (no auth required)POST /api/search/user-recovery— reads the hash (requires onlyuser_recovery:readACL)PATCH /api/_action/user/user-recovery/password— resets password using hash (no auth required)
Vulnerable code:
src/Core/System/User/Recovery/UserRecoveryDefinition.php—hashfield isApiAwarewith noReadProtection
Impact
- Full admin account takeover — attacker gains the highest privilege level in the system
- All admin capabilities — user/role management, system configuration, plugin management, customer data access
- Cascading compromise — taken-over admin account can be used to pivot to other attacks
- Low barrier —
user_recovery:readis a seemingly harmless permission that grants devastating access
Remediation
Remove the hash field from API responses:
// src/Core/System/User/Recovery/UserRecoveryDefinition.php
(new StringField('hash', 'hash'))
->addFlags(new Required(), new ApiAware(false)),
| Software | From | Fixed in |
|---|---|---|
shopware / platform
|
6.7.0.0 | 6.7.10.1 |
|
shopware / platform
|
- | 6.6.10.18 |
|
shopware / core
|
6.7.0.0 | 6.7.10.1 |
|
shopware / core
|
- | 6.6.10.18 |
Deep Security Visibility Without the Complexity
SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.
- No setup fees
- 5-min deployment
- Cancel anytime
Frequently Asked Questions
A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.
CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.
A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.
Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.
Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.
SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.