CVE-2025-61922 json
PrestaShop Checkout allows customer account takeover via email
published last yr. modified last mo. also GHSA-54hq-mf6h-48xh , EUVD-2025-34790
- cvss
- 9.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 43%
- public exploits
- 0
- none known
Summary
PrestaShop Checkout is the PrestaShop official payment module in partnership with PayPal. Starting in version 1.3.0 and prior to versions 4.4.1 and 5.0.5, missing validation on the Express Checkout feature allows silent login, enabling account takeover via email. The vulnerability is fixed in versions 4.4.1 and 5.0.5. No known workarounds exist.
Patch / fix
- packagist prestashop/ps_checkout 4.4.1, 5.0.5
- prestashop prestashop_checkout 7.4.4.1, 7.5.0.5, 8.4.4.1, 8.5.0.5, 9.5.0.5
Is CVE-2025-61922 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.50% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| GitHub | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | prestashop/ps_checkout | >=1.3.0, <4.4.1 >=5.0.0, <5.0.5 |
4.4.1 5.0.5 |
Affected products
- PrestaShopCorp ps_checkout
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
github.com
/PrestaShopCorp/ps_checkout/security/advisories/GHSA-54hq-mf6h-48xh
web, patch, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-61922
advisory
-
github.com
/PrestaShopCorp/ps_checkout
package
Sources
- CVE List CVE-2025-61922
- GitHub Advisory GHSA-54hq-mf6h-48xh
- NVD CVE-2025-61922
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.