PHP2Shell: Is your system affected? We can help straight away.
Whether it’s an online shop, a CMS or a digital experience platform: we’ll patch the security vulnerability, check for signs of an attack and support you with the next steps. If required, this includes hosting via our subsidiary, main cloud.
Two critical vulnerabilities in the PHP core
On 21 October 2026, two critical security vulnerabilities in PHP were disclosed: CVE-2026-109618 and CVE-2026-109619, commonly referred to as ‘PHP2Shell’. Both have a CVSS score of 9.2 out of 10. According to the BSI, exploitation could allow remote execution of malicious code. This does not require any authentication or user interaction.
The issue therefore affects PHP at a very fundamental level. The PHP project lists all PHP installations that process web requests, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed. The PHP project rates the risk as particularly high for mod_php.
For businesses, this means that it is not just the e-commerce platform or CMS used that is decisive. The PHP version and the actual server configuration are particularly relevant.
Current status
PHP version | Classification |
|---|---|
PHP 8.5.12 | Security fixes included |
PHP 8.4.27 | Security fixes included |
PHP 8.3.36 | Includes security fixes |
PHP 8.2.35 | Includes security fixes |
PHP 8.1 and earlier | No longer receives regular updates from the PHP project; backports may be available in some cases via distributions or LTS providers |
The PHP project recommends that all users update immediately. The BSI also classifies the situation as critical and recommends applying the patches provided without delay.
BSI warning ->
Three questions you should answer now
1. Is your shop, website or portal still running on a version of PHP that does not include the latest security patches?
2. Has your hosting provider restricted or updated PHP, or taken your application offline as a precaution?
3. Is your application so old or customised that a PHP update is not easily possible?
If you answer‘Yes’ or ‘Don’t know’ to at least one of these questions, you should have the situation checked.
You don’t need to find out for yourself which PHP configuration your server is using or which components might be affected. This is exactly where our quick check comes in. Together, we’ll clarifywhich PHP version is actually running, whether a direct update is possible, and what further steps would be advisable for your application.
An update patches the vulnerability. But had it already been exploited?
Installing the security updates is the most important first step. PHP explicitly states that only the update provides a complete solution to the known vulnerabilities. Temporary measures can reduce the attack surface, but they are no substitute for the update.
This raises a second question: what happened in the period leading up to the update?
After all, a successfully applied patch alone does not answer the question of whether an application had already been compromised.
We therefore distinguish between two tasks:
Action | What is this about? | Objective |
|---|---|---|
Rectify a security vulnerability | Update PHP to a patched version | Prevent further exploitation of known vulnerabilities |
System | Examine logs, files and any anomalies | Identify any indications of a previous compromise |
In addition to applying the patches, the BSI strongly recommends keeping a closer eye on exposed PHP web servers for any unusual behaviour.
In 15 minutes, you’ll know what to do next
Not every affected system requires the same action. For a current application, the PHP update may be implemented straight away. For older online shops, CMS systems or bespoke applications, however, some adjustments may be required first.
In a free 15-minute phone call, we’ll discuss the following together:
You will then receive a clear assessment of what the next step should be in your situation.
From initial analysis to stable operation
If a live shop or a business-critical application could be affected, it is not simply a matter of installing a new version of PHP as quickly as possible. The change must also be compatible with the existing application.
That is why we take a structured approach:
1. Initial analysis
2. Update or interim solution
If the update is possible, we will update PHP and then check the affected application. If the application cannot yet run on a current version of PHP, we will consider possible interim measures and the necessary migration path.
3. Compromise check
Where necessary, we investigate the system for any signs of an attack. These include, for example, suspicious access attempts, changes to files or other indications of a possible breach.
4. Functional test
Following an update, we test the application’s key functions. In the case of an online shop, these may include, for example, the front end, shopping basket, checkout, back end and relevant interfaces.
5. Curing and further measures
Once the immediate security measures are in place, we review the configuration and, where necessary, plan any required updates or upgrades.
6. Optional: ongoing operation
If required, our partner MainCloud can subsequently take over the technical operation.
Emergency assistance, inspection and modernisation – all from a single source
Services | What we do | Result |
|---|---|---|
Emergency patch | PHP update or necessary immediate measures and functional testing of the shop, CMS or application | Known security vulnerability patched and application checked |
Security check | Check for signs of attack, log analysis and review of suspicious changes | Documented findings and recommendations for action |
PHP migration | Code analysis, necessary adjustments, update to the latest PHP version and testing | Technically modernised PHP infrastructure |
Shopware migration | Modernisation of an existing Shopware 5 solution to Shopware 6 | Up-to-date e-commerce platform |
Managed hosting | Operation via main cloud in accordance with the agreed scope of services | Managed hosting and operational environment |
Can’t your application simply be updated?
The PHP2Shell vulnerability highlights a fundamental problem with older applications: what happens when the next version of PHP is required, but the existing application is no longer compatible?
The PHP project no longer provides regular updates for PHP 8.1 and older versions. However, it points out that individual Linux distributions and LTS providers may backport security fixes.
Anyone running a mature application should therefore not focus solely on the current security vulnerability.
We are checking:
1. Which components prevent the PHP upgrade
2. Which custom extensions are affected
3. Which dependencies need to be updated
4. What changes need to be made to the code
5. What tests are required before the system goes live
We can then gradually migrate the application to a modern PHP environment.
Even custom software that has evolved over time does not therefore need to be completely replaced overnight. The key is to have a realistic migration plan.
With Shopware 5, we’ll work with you to assess whether further customisations are still worthwhile or whether migrating to Shopware 6 is the better option.
To ensure it is clear who is responsible when the next security update is released
PHP2Shell also highlights how important clear lines of responsibility are during day-to-day operations.
Who monitors relevant security advisories? Who assesses the impact of an update on the application? Who deploys it? And who can step in if an update requires adjustments to the online shop or custom software?
This is where development and operations intersect.
elio knows the application and the code. main cloud takes care of the hosting and operations side on request. This allows technical development and day-to-day operations to be more closely coordinated.
Hanover data centre · ISO 27001 · 99.9% SLA · 24/7 on-call support · fixed monthly prices with no data transfer charges
Find out more about main cloud ->
When a PHP issue requires more than just a server update
A PHP security vulnerability involves several interrelated areas: the server, the PHP version, the application code, the shop system, extensions and interfaces.
Particularly with older or bespoke platforms, simply checking the server is therefore not always sufficient.
This is where elio comes in.
ISO/IEC 27001:2022 certified for our digital and IT services (BFMT Audit GmbH)
Experience in digital applications and eCommerce since 2000
100+ senior developers from Germany
Shopware Platinum Partner
OXID Enterprise Partner
Experience with e-commerce, CMS and bespoke projects
Offices in Gießen, Frankfurt am Main, Estenfeld and Heilbronn
Hosting and operation via main cloud, if required
Sie müssen kein bestehender elio-Kunde sein
Auch wenn Ihre Website, Ihr Onlineshop oder Ihre Individualanwendung von einem anderen Dienstleister entwickelt wurde, können wir die technische Situation zunächst gemeinsam mit Ihnen bewerten.
Let’s start by clarifying what your system actually needs
Not sure which version of PHP you’re using? Is your hosting provider asking you to update? Is your application no longer working with the latest version of PHP? Or has the update already been installed and you’d like to check if anything happened beforehand?
Then get started with the free quick check.
Briefly describe your situation to us. Together, we’ll look at your PHP version, application and hosting environment, and determine the next sensible steps.
Availability: Mon – Fri 09:00 – 12:30 · 13:30 – 17:00
Telephone: +49 641 968698-0
Email: business@elio-systems.com
elio GmbH, Gießen
Ihre Ansprechpartner
Sie haben Fragen zu unseren Leistungen oder zu elio? Wir sind für Sie da! Schreiben Sie uns einfach über das Kontaktformular, und wir melden uns schnellstmöglich bei Ihnen.