CVE-2025-61922

Affected versions

The issue was introduced in PrestaShop Checkout 1.3.0 .

All versions above 1.3.0 are vulnerable except of course the patch versions published on 16/10/2025: 7.4.4.1, 8.4.4.1, 7.5.0.5, 8.5.0.5, 9.5.0.5

Credits

We would like to thank Léo CUNÉAZ for reporting the issue.

Missing validation on Express Checkout feature allows silent log-in

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2025-61922 has a CVSS score of 9.1 (Critical). The vector is network-reachable, no 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 (5.0.5, 4.4.1); upgrading removes the vulnerable code path.

Kodem intelligence

The problem has been patched in versions

• v4.4.1 for PrestaShop 1.7 (build number: 7.4.4.1)
• v4.4.1 for PrestaShop 8 (build number: 8.4.4.1)
• v5.0.5 for PrestaShop 1.7 (build number: 7.5.0.5)
• v5.0.5 for PrestaShop 8 (build number: 8.5.0.5)
• v5.0.5 for PrestaShop 9 (build number: 9.5.0.5)

Read our Versioning policy to learn more about our build numbers and versions of PrestaShop Checkout

1. What is CVE-2025-61922? CVE-2025-61922 is a critical-severity improper authentication vulnerability in prestashop/ps_checkout (composer), affecting versions >= 5.0.0, < 5.0.5. It is fixed in 5.0.5, 4.4.1. The application does not adequately verify the identity of a user, device, or process before granting access.
2. How severe is CVE-2025-61922? CVE-2025-61922 has a CVSS score of 9.1 (Critical). 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 versions of prestashop/ps_checkout are affected by CVE-2025-61922? prestashop/ps_checkout (composer) versions >= 5.0.0, < 5.0.5 is affected.
4. Is there a fix for CVE-2025-61922? Yes. CVE-2025-61922 is fixed in 5.0.5, 4.4.1. Upgrade to this version or later.
5. Is CVE-2025-61922 exploitable, and should I be worried? Whether CVE-2025-61922 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-2025-61922 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-2025-61922?
   • Upgrade prestashop/ps_checkout to 5.0.5 or later
   • Upgrade prestashop/ps_checkout to 4.4.1 or later