CVE-2025-61922 Zero-Click Account Takeover on Prestashop #1729
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🤖 Automated Content Update
This PR was automatically generated by the HackTricks News Bot based on a technical blog post.
📝 Source Information
🎯 Content Summary
Vulnerability: CVE-2025-61922 (CVSS 9.1,
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N) in the PrestaShop module ps_checkout (PrestaShop Checkout) affects versions < 5.0.5. The blog shows this is a zero-click customer account takeover caused by missing validation in the Express Checkout flow that enables a silent login for an arbitrary customer if the attacker knows the victim’s email address.Why this is critical (impact):...
🔧 Technical Details
orderID), downstream action classes may treat other DTO fields as trusted. If any downstream logic uses those fields to decide authentication/identity, it can become an auth bypass.2) “Login by email existence” → account takeover: Any flow that does
customerId = customerExists(email)(or similar lookup), then constructs an identity object (new Customer(customerId)) and calls a session/context switch primitive (e.g.,context->updateCustomer(customer)) without verifying ownership of that email (password, signed token, IdP assertion, etc.) allows takeover of arbitrary accounts by supplying the victim’s email in a crafted request. Exploitation typically requires identifying the exact JSON/parameter path used (here: <...🤖 Agent Actions
Summary:
Tests: Not applicable (documentation update).
This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.