Prestashop
Prestashop
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
Official registry publication history is available at prestashop, but registry activity is not a publisher support boundary.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-84186 | 7 Sep 2026 | < 9.1.5; < 8.2.8 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-44212 | 14 May 2026 | < 8.2.6; >= 9.0.0-alpha.1, < 9.1.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-33674 | 26 Mar 2026 | < 8.2.5; >= 9.0.0-alpha.1, < 9.1.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-33673 | 26 Mar 2026 | >= 9.0.0-alpha.1, < 9.1.0; < 8.2.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-25597 | 6 Feb 2026 | < 8.2.4; >= 9.0.0-alpha.1, < 9.0.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-1230 | 12 Feb 2025 | 8.1.7 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-34717 | 14 May 2024 | = 8.1.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-34716 | 14 May 2024 | >= 8.1.0, < 8.1.6 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-26129 | 19 Feb 2024 | >= 8.1.0, < 8.1.4 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2024-21628 | 2 Jan 2024 | < 8.1.3 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2024-21627 | 2 Jan 2024 | >= 8.0.0, < 8.1.3; < 1.7.8.11 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2023-43664 | 28 Sep 2023 | < 8.1.2 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2023-43663 | 28 Sep 2023 | < 8.1.2 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2023-39530 | 7 Aug 2023 | < 8.1.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2023-39529 | 7 Aug 2023 | < 8.1.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2023-39528 | 7 Aug 2023 | < 8.1.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2023-39527 | 7 Aug 2023 | < 1.7.8.10; >= 8.0.0, < 8.0.5; = 8.1.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2023-39526 | 7 Aug 2023 | < 1.7.8.10; >= 8.0.0, < 8.0.5; = 8.1.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2023-39525 | 7 Aug 2023 | < 8.1.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2023-39524 | 7 Aug 2023 | < 8.1.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2023-30839 | 25 Apr 2023 | >= 8.0.0, < 8.0.4; < 1.7.8.9 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2023-30838 | 25 Apr 2023 | >= 8.0.0, < 8.0.4; < 1.7.8.9 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2023-30545 | 25 Apr 2023 | < 1.7.8.9; >= 8.0.0, < 8.0.4 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2023-25170 | 13 Mar 2023 | >= 1.7.0.0, < 8.0.1 | 8.0.1. | Update reference ↗ |
| CVE-2022-46158 | 8 Dec 2022 | < 1.7.8.8 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-31181 | 1 Aug 2022 | >= 1.6.0.10, < 1.7.8.7 | 1.7.8.7. | Update reference ↗ |
| CVE-2022-21686 | 26 Jan 2022 | >= 1.7.0.0, < 1.7.8.3 | 1.7.8.3. | Update reference ↗ |
| CVE-2021-43789 | 7 Dec 2021 | >= 1.7.5.0, <= 1.7.8.1 | 1.7.8.2. | Update reference ↗ |
| CVE-2021-21398 | 30 Mar 2021 | >= 1.7.7.0, < 1.7.7.3 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-21308 | 26 Feb 2021 | >= 1.5.0, < 1.7.7.2 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-21302 | 26 Feb 2021 | >= 1.5.0, < 1.7.7.2 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2020-26224 | 16 Nov 2020 | >= 1.4.10.0 < 1.7.6.9 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-15162 | 24 Sep 2020 | > 1.5.0.0, < 1.7.6.8 | 1.7.6.8. | Update reference ↗ |
| CVE-2020-15160 | 24 Sep 2020 | >= 1.7.5.0, < 1.7.6.8 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2020-15161 | 24 Sep 2020 | > 1.6.0.4, < 1.7.6.8 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2020-4074 | 2 Jul 2020 | >= 1.5.0.0, < 1.7.6.6 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2020-15082 | 2 Jul 2020 | >= 1.6.0.1, < 1.7.6.6 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2020-15083 | 2 Jul 2020 | >= 1.7.0.0, < 1.7.6.6 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2020-11074 | 2 Jul 2020 | >= 1.5.3.0, < 1.7.6.6 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2020-15079 | 2 Jul 2020 | >= 1.5.0.0, < 1.7.6.6 | 1.7.6.6 | Update reference ↗ |
| CVE-2020-15080 | 2 Jul 2020 | >= 1.7.4.0, <1.7.6.6 | 1.7.6.6 | Update reference ↗ |
| CVE-2020-15081 | 2 Jul 2020 | >= 1.5.0.0, < 1.7.6.6 | 1.7.6.6. | Update reference ↗ |
| CVE-2020-5286 | 20 Apr 2020 | >= 1.7.4.0, < 1.7.6.5 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2020-5287 | 20 Apr 2020 | > 1.5.5.0, < 1.7.6.5 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2020-5288 | 20 Apr 2020 | >= 1.7.0.0, < 1.7.6.5 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2020-5293 | 20 Apr 2020 | >= 1.7.0.0, < 1.7.6.5 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2020-5271 | 20 Apr 2020 | >= 1.6.0.0, < 1.7.6.5 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2020-5272 | 20 Apr 2020 | >= 1.5.5.0, < 1.7.6.5 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2020-5276 | 20 Apr 2020 | >= 1.7.1.0, < 1.7.6.5 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2020-5278 | 20 Apr 2020 | >= 1.5.4.0, < 1.7.6.5 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.