Cpe:2.3:a:thirtybees:thirty_bees:*:*:*:*:*:*:*:* - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/cpes/cpe2.3athirtybeesthirty_bees/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioMon, 12 Oct 2026 18:33:44 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgAuthentication Bypass in Thirty bees PasswordControllerhttps://feed.craftedsignal.io/briefs/2026-10-thirty-bees-auth-bypass/Mon, 12 Oct 2026 18:33:44 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-10-thirty-bees-auth-bypass/Thirty bees versions up to 1.7.0 are vulnerable to an authentication bypass in PasswordController::resolveCustomer() that enables account takeover via manipulated guest checkout processes.Thirty bees through version 1.7.0 contains an authentication bypass vulnerability located in the PasswordController::resolveCustomer() method. This vulnerability stems from improper validation of guest account tokens, which allows an unauthenticated remote attacker to reset the passwords of registered customers. The attack requires the platform to have the guest checkout functionality enabled. By placing a guest order using a targeted victim's email address, an attacker can obtain a guest secure key. This key is then abused to manipulate the password reset flow, effectively allowing the attacker to take over the victim's account. This flaw poses a significant risk to user data integrity and account security for e-commerce sites running affected versions of the Thirty bees platform.

Impact

Successful exploitation results in full account takeover of registered customers on affected e-commerce platforms. Attackers can gain unauthorized access to customer account information, order history, and potentially payment-related data linked to the profile. This vulnerability impacts any organization running Thirty bees version 1.7.0 or earlier with guest checkout enabled.

Recommendation

Prioritized actions for administrators of Thirty bees environments:

  • Immediately audit current configurations to determine if guest checkout is enabled, as this is a prerequisite for exploitation.
  • Monitor application logs for anomalous password reset requests or unexpected patterns associated with guest checkout flows.
  • Verify if an update is available from the vendor that patches the PasswordController::resolveCustomer() method and apply it immediately to address CVE-2026-109394.
  • If no patch is available, consider disabling the guest checkout functionality until a secure version is deployed.
]]>highadvisoryauthentication-bypasse-commerceaccount-takeover