CVE-2026-48009

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:

1. POST /api/_action/user/user-recovery, triggers recovery, creates hash in DB (no auth required)
2. POST /api/search/user-recovery, reads the hash (requires only user_recovery:read ACL)
3. PATCH /api/_action/user/user-recovery/password, resets password using hash (no auth required)

Vulnerable code:

• src/Core/System/User/Recovery/UserRecoveryDefinition.php, hash field is ApiAware with no ReadProtection

• 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:read is a seemingly harmless permission that grants devastating access

CVE-2026-48009 has a CVSS score of 6.8 (Medium). The vector is network-reachable, low 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

Remove the hash field from API responses:

// src/Core/System/User/Recovery/UserRecoveryDefinition.php
(new StringField('hash', 'hash'))
    ->addFlags(new Required(), new ApiAware(false)),

1. What is CVE-2026-48009? CVE-2026-48009 is a medium-severity security 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.
2. How severe is CVE-2026-48009? CVE-2026-48009 has a CVSS score of 6.8 (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-48009?
   • 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-48009? Yes. CVE-2026-48009 is fixed in 6.7.10.1, 6.6.10.18. Upgrade to this version or later.
5. Is CVE-2026-48009 exploitable, and should I be worried? Whether CVE-2026-48009 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-48009 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-48009?
   • 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