Urgent PrestaShop Security Alert: Patch Your PHP Servers Against 'php2shell' CVEs Immediately
Urgent PrestaShop Security Alert: Patch Your PHP Servers Against 'php2shell' CVEs Immediately
At Migrate My Shop, we understand that the security of your PrestaShop store is paramount. In the fast-evolving landscape of e-commerce, staying ahead of potential threats is not just good practice—it's essential for business continuity and customer trust. Today, we're addressing a critical security alert that directly impacts every PrestaShop merchant: the 'php2shell' vulnerabilities.
On October 21, 2026, two severe PHP vulnerabilities, identified as CVE-2026-109618 and CVE-2026-109619, were disclosed. Each carries an alarming CVSS score of 9.2, indicating critical severity. Dubbed 'php2shell', these bugs are not in PrestaShop's code itself, but in the underlying PHP engine that powers your entire e-commerce operation. This means every PrestaShop store, regardless of its version, is potentially at risk if its PHP server isn't patched.
Inspired by a vital discussion on the PrestaShop forum by Knowband Plugins, this article serves as your comprehensive guide to understanding these threats and, more importantly, taking immediate action to secure your shop. As experts in PrestaShop migrations and maintenance, we emphasize that proactive security measures are always cheaper and less disruptive than reactive damage control.
Understanding the 'php2shell' Threat: Memory Exhaustion and State Leakage
The 'php2shell' vulnerabilities are insidious because they exploit fundamental aspects of how PHP processes requests. They don't require a login, an admin password, or even a customer account. A specially crafted HTTP request is all an attacker needs to potentially compromise your server.
- CVE-2026-109618 (Memory Exhaustion): This bug occurs when PHP's memory management is interrupted at a critical moment. If a request is cut off improperly, the data structures can be left in a half-configured state. Subsequent cleanup processes might misinterpret this corrupted state, leading to crashes or unintended behavior.
- CVE-2026-109619 (State Leakage): The reverse of the first, this vulnerability involves data from a previous request lingering in memory after it should have been freed. A later request, processed by the same PHP worker, could then inadvertently access or manipulate this stale data.
The PHP Security Team has confirmed that these vulnerabilities could lead to severe consequences, including server crashes, sensitive data exposure, or even remote code execution (RCE). RCE is the most dangerous, allowing attackers to run arbitrary code on your server, potentially taking full control of your PrestaShop store and its data.
Why PrestaShop Updates Aren't the Fix
This is a crucial point that often causes confusion. Many PrestaShop merchants assume that keeping their PrestaShop core, modules, and themes updated will protect them from all threats. While regular PrestaShop updates are vital for security and functionality, they will not address the 'php2shell' vulnerabilities.
The flaws reside deep within the PHP engine itself, meaning an attack can occur even before a single line of your PrestaShop application code, Smarty templates, or any installed module has a chance to execute. This is why core PrestaShop updates, module updates, or cache clears are ineffective against 'php2shell'. Only a PHP update can fix these specific issues.
Furthermore, these vulnerabilities are not tied to a specific PHP execution environment. Whether your PrestaShop store runs on PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP, or LiteSpeed, your server is susceptible. In fact, `mod_php` carries the highest risk due to its tight integration with the web server, allowing attacks to fire even earlier in the request lifecycle.
Action Required: Checking and Patching Your PHP
Immediate action is required. Here's how to proceed:
How to Identify Your PHP Version
The first step is to know what PHP version your PrestaShop store is currently running:
- Log into your PrestaShop Back Office.
- Navigate to Advanced Parameters > Information.
- Your PHP version will be clearly displayed there.
The patched PHP releases are 8.5.12, 8.4.27, 8.3.36, and 8.2.35. Backports have also been released for older, unsupported versions like 7.4, 8.0, and 8.1.
The Nuance of "Patched" Versions
Here's the catch: simply seeing a version number that looks older than the patched ones doesn't automatically mean you're vulnerable, and a newer-looking version isn't a guarantee of safety. Linux distributions often apply security patches to their PHP packages without changing the main version number. This means an older-looking version might already contain the fix, while a seemingly newer one might not if it's from a different branch or hasn't been updated by your host.
The critical question is whether the *installed package* has the specific fix for CVE-2026-109618 and CVE-2026-109619. Only your hosting provider or the distribution's security notes can confirm this definitively.
For Shared or Managed Hosting Users
If your PrestaShop store is on shared or managed hosting, you cannot directly patch PHP. Your responsibility is to contact your hosting provider immediately. We recommend sending a clear, concise inquiry:
Subject: Urgent Security Inquiry: PHP 'php2shell' Vulnerabilities (CVE-2026-109618 & CVE-2026-109619)
Dear [Hosting Provider Support Team],
We are writing to inquire about the status of critical PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619, known as 'php2shell'.
Could you please confirm in writing if these vulnerabilities have been fixed on the servers hosting our account [Your Domain Name/Account ID]? Furthermore, please confirm that all PHP processes were restarted after the patch was applied.
We would also appreciate knowing which specific PHP package version is currently installed on our server.
Thank you for your prompt attention to this urgent matter.
Sincerely,
[Your Name/Company Name]Insist on a written reply that specifically mentions the CVE numbers and confirms a restart. A vague answer like "secure" or "up to date" is insufficient. An update that was installed but not reloaded means the old, vulnerable code is still running.
The EU joint statement (ENISA, CERT-EU, Europol EC3) echoes this advice: identify all PHP-based applications, engage with hosting providers, and prioritize internet-facing systems, including staging environments.
For Self-Managed Servers (VPS, Dedicated, Docker)
If you manage your own VPS, dedicated server, or Docker containers, the patching responsibility falls directly on you:
- Update PHP: Use your distribution's package manager (e.g., `apt update && apt upgrade php` on Debian/Ubuntu, `yum update php` on CentOS/RHEL) to install the latest patched PHP packages.
- Restart Services: After updating, you must restart all services that serve PHP. This includes PHP-FPM, Apache, LiteSpeed, or FrankenPHP. If multiple services share the machine, ensure each is restarted.
- Docker Environments: For Docker, simply restarting an old container is not enough. You must rebuild your Docker image on a patched base image to incorporate the fixes.
Always verify the update was successful and the services are running correctly after the restart.

What If You Can't Patch Immediately?
While immediate patching is the only complete solution, the PHP team acknowledges that sometimes delays are unavoidable. In such cases, temporary mitigations can reduce, but not eliminate, your exposure:
- Adjust `post_max_size` and `upload_max_filesize`: Lowering these values in your `php.ini` (or FPM pool/server config) can make it harder for attackers to send large, specially crafted requests. Be cautious not to set them too low, as this could break legitimate imports and file uploads in your PrestaShop store.
- Disable `session.upload_progress.enabled=0`: This can be set in `php.ini` or server configuration.
- Disable `fatal_error_backtraces=0` (PHP 8.5 only): Also set in `php.ini` or server configuration.
Important: These settings must be applied in `php.ini`, the FPM pool configuration, or the main server config. Using `ini_set` or `.user.ini` will not work for these specific directives. And remember, none of these changes take effect until your PHP workers are restarted.
A Web Application Firewall (WAF) can provide an additional layer of defense, but it's not a substitute for patching. WAFs can be bypassed if the origin server is directly accessible. Ensure your server is configured to accept traffic only from your WAF.
If patching must be delayed significantly, the EU guidance suggests isolating exposed applications from the public network until they can be secured. For a live PrestaShop store, this might mean temporarily putting it into maintenance mode or behind a robust firewall with strict access rules.
Addressing Older PHP Versions and End-of-Life
The 'php2shell' vulnerabilities highlight a broader issue for many PrestaShop merchants: running on outdated PHP versions. PHP 8.1 and below no longer receive regular security updates. For these versions, you must specifically inquire about backports for CVE-2026-109618 and CVE-2026-109619. The version string alone won't tell you if a backport is installed.
Furthermore, PHP 8.2 reaches its official End-of-Life (EOL) on December 31, 2026. This means no further security updates, even for critical vulnerabilities, will be released for PHP 8.2 after this date. If your PrestaShop store is still on PHP 8.2 or older, this is a compelling reason to plan an upgrade to a newer, supported PHP version (like PHP 8.3 or 8.4, which PrestaShop 9 supports). This often involves a PrestaShop migration, which is where Migrate My Shop excels.
Maintaining an up-to-date PHP environment is fundamental to the long-term security and performance of your PrestaShop store. It's a small habit that pays off immensely: always document your PHP version, your host's responses, and when any restarts occurred. This saves significant time and effort in future security audits or troubleshooting.
Conclusion: Act Now, Stay Secure
The 'php2shell' vulnerabilities are serious, but they don't call for panic. They call for immediate, informed action. Check your PHP version, contact your hosting provider with precise questions, or patch your self-managed servers without delay. The technical steps are often less complex than the organizational effort of getting clear answers and ensuring restarts.
At Migrate My Shop, we are committed to helping PrestaShop merchants navigate complex technical challenges, including security updates and version compatibility. If you're running an older PrestaShop version, struggling with PHP compatibility, or considering a full migration to a newer, more secure PrestaShop environment, our experts are here to assist. Don't let security vulnerabilities compromise your e-commerce success.
Sources
- PHP: https://www.php.net/archive/2026.php
- PrestaShop advisory: https://build.prestashop-project.org/news/2026/php-security-updates-october-2026/
- EU joint statement (ENISA): https://www.enisa.europa.eu/news/joint-statement-on-critical-php-vulnerabilities
- Knowband Security Advisory: https://www.knowband.com/blog/prestashop-blog/critical-php-vulnerabilities-updates-2026/