Attention to "silent login": critical vulnerability in the PrestaShop Checkout module (CVE-2025-61922)

In the world of e-commerce, payment and checkout forms are a sensitive target for cyber attacks. A vulnerability CVE-2025-61922 affecting the official PrestaShop Checkout module, developed in collaboration with PayPal, was recently made public. This flaw allows a customer account takeover without visible interaction ("silent login"). In this article we analyze what it is, what the implications are for those running a PrestaShop-based store, and what immediate countermeasures to take.

Technical detail of vulnerability

  • The PrestaShop Checkout module, in versions starting from 1.3.0 and up before versions 4.4.1 and 5.0.5, has a validation failure on the "Express Checkout" feature.

  • Specifically: a remote attacker, without the need for privileges or user interaction, can trigger a "silent" login via email (bypass authentication logic) and take over the customer account.

  • The reported CVSS 3.1 score is 9.1 (critical): attack vector AV:N, low complexity, no privilege required, no user interaction required, high impact on confidentiality and integrity.

  • The problem is classified as CWE-287 (Improper Authentication): the system does not adequately verify the identity of the actor.

  • No alternative solutions or effective workarounds are indicated: fix is available only by updating the module.

Implications for an e-commerce based on PrestaShop

For an e-commerce site using PrestaShop Checkout, the consequences can be severe:

  • Account takeover: a registered customer may not notice, and the attacker could view or modify sensitive data, orders, history, potentially add means of payment.

  • Trust/reputation: abuse of an authentication flaw in a payment form undermines user trust and could have legal consequences (GDPR) if personal data is exposed.

  • Impacts on business continuity: if an attacker compromises accounts, generates fraud, penalties or claims, e-commerce operations may be compromised.

  • Module compatibility/overrides: in contexts with customizations (overridden modules, modified hooks, checkout overrides), the risk is that the vulnerability may be amplified or less obvious.

What to do now - recommended countermeasures

Primary solution

  • Check the version of the PrestaShop Checkout module installed. If you are using an older version than 4.4.1 or older than 5.0.5 (depending on the branch you are using), you should update promptly.

  • Apply the update to the official module: version 4.4.1 or 5.0.5 or higher.

Additional verification

  • Check for custom overrides or "forked" checkout modules that may not include the patch.

  • Inspects user access logs for suspicious activity: unexpected logins, sessions generated without user action, address or payment method changes in customer profiles.

  • Checks that backup and recovery procedures are effective, in case of compromise: useful for rollback and forensic analysis.

Temporary mitigation measures (in case the update cannot be immediate)

  • If possible, temporarily disable the "Express Checkout" feature or restrict access only to authenticated users with an active session.

  • Strengthens login controls: enable client-side MFA (multi-factor authentication) if supported, send login/activity notifications to clients.

  • Sets up strengthened anomaly monitoring: logins from geographically unusual IPs, too many anonymous checkout requests, etc.

Residual risks and further considerations

  • Even after the patch, if the PrestaShop installation has deep customizations or third-party modules that touch the checkout/login flow, it is necessary to verify end-to-end that the patch is indeed active and that no backdoors or bypasses are still possible.

  • Although the likelihood of exploits is estimated to be low (see EPSS ~0.04% according to Snyk), the severity of the impact (account takeover, loss of integrity and confidentiality) implies that caution is high.

  • It should be considered that the attacker does not require user interaction or privileges: this accelerates the criticality of the vulnerability.

  • It is good practice to include the vulnerability in one's internal "vulnerability management" programming: document affected version, patch date, post-patch testing, observation period.

Conclusion

For those running a PrestaShop-based e-commerce site, vulnerability CVE-2025-61922 is a situation to prioritize: it impacts a critical module (checkout/payment), enables customer account takeovers with high severity, and requires no user interaction or privileges. The recommended action is an immediate upgrade of the PrestaShop Checkout module to the correct versions, coupled with operational security audits and checks.

Reference:

Product added to wishlist