Skip to content
← All articles

Guides · · 5 min read

PrestaShop 1.7 end of life: what it means for your store

PrestaShop 1.7 gets no more updates, not even security fixes, and it cannot run on a supported PHP version. What that means in practice, how much time you really have, and the three ways forward.

Illustration of moonlit lavender hills with a card showing PrestaShop 1.7 marked end of life, PHP 7.4 without security fixes, and the way through 8.2 to PrestaShop 9

PrestaShop 1.7 still runs thousands of stores, and most of them work fine day to day. But the version is finished: PrestaShop does not fix it any more, and the PHP versions it runs on have had no security fixes for years. Nothing breaks on a given date. The risk simply grows every month.

This article explains what "end of life" means for a 1.7 store, where the real deadlines are, and what you can do about it.

Is PrestaShop 1.7 still supported?

No. The facts, all from PrestaShop's own sources:

  • The last 1.7 release was 1.7.8.11, on 2 January 2024. There has been no 1.7 release since.
  • PrestaShop supports only the newest minor version. Its contribution guidelines say that once a new "dot-zero" version is out, no new patch releases are made for older versions, apart from rare exceptions. 8.0 came out in October 2022 and 9.0 in June 2025, so 1.7 is now two major versions behind.
  • Security holes found now stay open in 1.7. In August 2026 PrestaShop fixed an SQL injection in back-office list filters in 8.2.8 and 9.1.5. The advisory says the same flawed code "is also present in 1.7.x and earlier, which are end of life and will not receive a patch."

So a 1.7 store gets no core fixes at all. Whatever is found from now on is fixed only in 8.2 and 9.

The bigger problem: PHP

PrestaShop 1.7.8 runs on PHP 7.1 to 7.4, and older 1.7 versions stop even earlier. None of them run on PHP 8.

PHP version Security fixes ended
7.1 1 December 2019
7.2 30 November 2020
7.3 6 December 2021
7.4 28 November 2022

So the PHP under every 1.7 store has had no security fixes for at least three years. That matters more than the PrestaShop core itself: PHP handles every request, and a hole in it is a hole in every site that runs on it.

It also has a practical side. Hosting companies keep PHP 7.x running for old sites, but some charge extra for it, and sooner or later a server move or a control-panel update removes it. On that day a 1.7 store does not run at all, and an upgrade turns from a project into an emergency. For the full table of which PrestaShop version runs on which PHP, see PrestaShop and PHP versions.

What else gets harder

  • Modules. Each module developer decides how long to support 1.7, and some new versions, security fixes included, come out only for 8 and 9. A payment module that stops getting updates is the one that hurts most.
  • Security advisories for modules. Friends of Presta publishes holes found in PrestaShop modules. The fixed module version can need a newer PrestaShop than 1.7.
  • Help. Fewer developers want to work on 1.7 and PHP 7, and the answers you find online are increasingly about 8 and 9.

How much time do you have?

There is no switch-off date. A 1.7 store keeps working until something forces a change: the host drops PHP 7.4, a payment module stops working, or a hole is used against the store. You don't choose when that happens, so the real question is whether you upgrade on your own schedule or on someone else's.

A planned upgrade takes weeks of calm work on a copy of the store. The same job done after the store has gone down takes the same work, but under pressure and with lost sales.

Your three options

1. Stay on 1.7 for now and reduce the risk. A reasonable short-term plan if an upgrade is not possible this season:

  • keep every module at its latest 1.7-compatible version, payment modules first;
  • remove modules you don't use, since every installed module is code that can have a hole;
  • protect the back office: a private admin URL, strong passwords, two-factor login through a module, access limited by IP if you can;
  • follow the Friends of Presta security advisories for the modules you use;
  • keep tested backups that you can restore.

None of this fixes PHP 7.x, so treat it as a bridge, not a plan.

2. Upgrade to 8.2. PrestaShop 8.2 still gets security fixes until PrestaShop 10 is released. It is also the step every 1.7 store goes through on the way to 9. The catch is PHP again: PrestaShop 8 runs on PHP 8.1 at most, and PHP 8.1 has had no security fixes since 31 December 2025. Stopping at 8.2 means doing most of the work and still ending up on an unsupported PHP.

3. Upgrade to PrestaShop 9. PrestaShop 9 runs on PHP 8.1 to 8.5 (9.1 and 9.2), so the server can move to a PHP version with years of security fixes left. The way goes through 8.2: the copy of the store is upgraded to 8.2, checked, and then upgraded to 9. The live store moves only once. Our step-by-step test of a 1.7.6 store upgraded to 9.2 shows what breaks along the way and how long each step takes.

For most stores the third option is the right one, because it is the only one that ends on a supported PHP version.

Where to start

  1. Check the version. If you are not sure which version a store runs on, the PrestaShop version check tells it from the store's address in a few seconds, together with the theme and the modules it can see.
  2. See what would break. Our free PrestaShop 9 readiness check is a module that reads your modules, theme and overrides from inside the store and lists what would stop working on PrestaShop 9. It runs on 1.7 and changes nothing.
  3. Decide with the list in hand. The list shows how big the job is, so you can plan it, budget it, or hand it over.

Need a hand?

We upgrade PrestaShop 1.7 and 8 stores to version 9 for a fixed price from €900, always on a copy first, so the live store keeps selling until the switch. You get the exact price before any work starts.

Have a project in mind?

Tell us what you are building. You will get a concrete proposal with price and timeline within 24 hours.

Get a proposal