Urgent PrestaShop Security Alert: Are Your PHP Servers Patched Against php2shell?

Urgent PrestaShop Security Alert: Are Your PHP Servers Patched Against php2shell?

A critical security alert has shaken the PHP world, directly impacting all PrestaShop store owners. Two severe PHP vulnerabilities, dubbed "php2shell" (CVE-2026-109618 and CVE-2026-109619), were disclosed on October 21, 2026, each boasting a CVSS score of 9.2. Given PrestaShop's fundamental reliance on PHP, it's imperative for every merchant to verify their server's patch status. This insight, inspired by a vital PrestaShop forum thread by Knowband Plugins, breaks down what you need to know and how to protect your e-commerce business.

Understanding the php2shell Vulnerabilities:

These aren't bugs within PrestaShop's code but rather in the core PHP engine itself. The first vulnerability involves memory exhaustion, where an interrupted PHP request can leave corrupted data. The second is a state leakage issue, where data from a previous request remains accessible to a subsequent one. Both can be exploited via specially crafted HTTP requests, potentially leading to server crashes, data exposure, or even remote code execution – all without requiring any login credentials. This means your shop is vulnerable even before a single line of PrestaShop code executes.

Why PrestaShop Updates Won't Save You:

It's crucial to understand that updating your PrestaShop core, modules, or clearing cache will not resolve these PHP-level vulnerabilities. Since the flaws reside in the PHP engine, only a PHP update can fix them. The PrestaShop advisory itself confirms that a major PrestaShop upgrade is a separate, non-emergency task. Furthermore, all common PHP execution environments – PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP, and LiteSpeed – are susceptible.

How to Check Your PHP Version and Patch Status:

  1. Find your PHP version: Log into your PrestaShop Back Office, navigate to Advanced Parameters > Information. Your PHP version will be displayed there.
  2. Identify patched versions: The officially patched PHP releases are 8.5.12, 8.4.27, 8.3.36, and 8.2.35, with backports available for older versions like 7.4, 8.0, and 8.1.
  3. The critical caveat: Simply seeing a "new" version number isn't definitive proof of a patch. Many Linux distributions apply security fixes without altering the main version string. The ultimate confirmation must come from your hosting provider or the distribution's security notes.

Action Steps for PrestaShop Merchants:

  • Shared or Managed Hosting: You cannot patch PHP yourself. Immediately contact your hosting provider. Ask explicitly: "Are CVE-2026-109618 and CVE-2026-109619 fixed on my servers, and were all PHP processes restarted afterwards?" Insist on a written reply that mentions the CVE numbers and confirms a restart. A generic "secure" or "up-to-date" response is insufficient.
  • Self-Managed Servers (VPS/Dedicated): You are responsible for the update. Update your PHP packages (e.g., via your distribution's package manager) and then restart all services that serve PHP (PHP-FPM, Apache, LiteSpeed, etc.). If using Docker, rebuild your images on a patched base, as restarting an old container offers no protection.
  • Staging Environments: Don't forget any internet-facing staging or development copies. They are just as vulnerable as your live shop.

Temporary Mitigations (If Immediate Patching Isn't Possible):

While no complete mitigation exists short of patching, you can reduce exposure:

  • Lower post_max_size and upload_max_filesize in your php.ini or server configuration. Be cautious, as setting them too low can break imports or file uploads.
  • Set session.upload_progress.enabled=0.
  • For PHP 8.5 only, set fatal_error_backtraces=0.
  • Important: These settings must be applied in php.ini, the FPM pool configuration, or server config files. ini_set or .user.ini will not work. Remember to restart PHP workers after making these changes.
  • A Web Application Firewall (WAF) can add an extra layer of defense but is not a substitute for patching. Ensure your server only accepts traffic from the WAF.

Older PHP Versions and End-of-Life:

PHP 8.1 and older no longer receive regular updates, making backports crucial. PHP 8.2 reaches its end-of-life on December 31, 2026, making an upgrade plan to a newer, supported version essential.

Conclusion:

This situation calls for vigilance, not panic. Proactive communication with your hosting provider or prompt action on self-managed servers is key. Documenting your PHP version, host responses, and restart times can save significant hassle later. Your PrestaShop store's security depends on it.

(Source: PrestaShop Forum Thread #1111132 by Knowband Plugins)

Start with the tools

Explore migration tools

See options, compare methods, and pick the path that fits your store.

Explore migration tools