Why PrestaShop stores are exposed
The flaws, CVE-2026-109618 and CVE-2026-109619, are in PHP itself and can let someone run code on the server without logging in. PHP fixed them in 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP 8.1 and older get no update from PHP, only source fixes for people who build PHP themselves and fixes some Linux vendors provide (PHP's advisory). The full story.
The PrestaShop 8 catch
PrestaShop's own requirements for versions 8.0 to 8.2 list PHP 7.2 to 8.1, with 8.1 recommended, and PHP 8.2 or newer as not supported (PrestaShop 8 requirements). So a PrestaShop 8 store cannot simply switch to a fixed PHP 8.2 or newer. It needs either a host that backports the fix to PHP 8.1, or an upgrade of the store.
PrestaShop 9 supports PHP 8.1 to 8.4 (9.0) and up to 8.5 (9.1), with 8.4 and 8.5 recommended (PrestaShop 9 requirements).
What to do
- Find your PrestaShop version (in the back office) and your PHP version (in your hosting panel). The 5-minute check.
- On PHP 8.1 or older: ask your host in writing whether that PHP carries a fix for CVE-2026-109618 and CVE-2026-109619.
- If not: plan the move to PrestaShop 9 on a fixed PHP. Test it on a copy first: modules and themes may need updates too.
- Meanwhile, ask your host to apply the temporary settings PHP lists. How to update PHP lists them.
- Keep fresh backups of the files and the database off the server, and watch for signs of a hack. What to do if it happens.
Does your store need to be a store?
Some PrestaShop sites sell little online and mostly show products for people to call or visit. If that is yours, a site with no PHP, no modules and nothing to update may serve you better than a store to keep patched: a website without maintenance. If you sell online every day, keep PrestaShop and keep it current.