
PHP Security Vulnerability 2026: Is your website at risk?
29. October 2026
The critical PHP vulnerability known as PHP2Shell puts unpatched websites at risk. Find out which PHP versions are affected and how to reliably protect your website…
Overview
- You'll learn how the critical PHP vulnerability PHP2Shell works and what risks it poses to your website.
- You'll learn which PHP versions are affected and how to check for security updates and ensure your website is protected.
- You'll discover why updates alone aren't enough and what additional measures can protect your website from cyberattacks.
The PHP security vulnerability affects a core technology used by many business websites, online shops, and WordPress installations. Two critical vulnerabilities known as PHP2Shell have been disclosed, which under certain conditions allow attackers to execute arbitrary code. Security updates were released on October 21. However, you should not assume that your website is automatically protected.
What matters is which PHP version is actually running on your server and whether your hosting provider has applied the fixes. This also raises an important question: Could an attack have already occurred before the update?
Here you can find out who is affected, how to check your protection, and what steps you should take now.
What is the 2026 PHP security vulnerability?
PHP2Shell refers to two critical security vulnerabilities in the PHP core: CVE-2026-109618 and CVE-2026-109619. Both affect memory management. On vulnerable servers, attackers can execute their own code without authentication under certain conditions. Each vulnerability has a severity score of 9.2 out of 10 according to CVSS 4.0.
PHP processes dynamic content on the server side. This makes the technology relevant for WordPress, Drupal, Joomla, and numerous online shops, among others.
PHP processes dynamic content on the server side. This makes the technology relevant for WordPress, Drupal, Joomla, and numerous online shops, among others.
- CVE-2026-109618: Error during memory cleanup following a memory limit event.
- CVE-2026-109619: Outdated internal memory references may continue to be used after an error occurs.
This does not mean that every PHP website has already been hacked. The specific risk depends, among other things, on the PHP version and server configuration.
Why is PHP2Shell dangerous for businesses?
If an attacker successfully exploits such a vulnerability, they can act with the permissions of the PHP process on the server. Possible consequences range from manipulated websites and outages to access to sensitive data. For companies, this creates risks to customer trust, business processes, and website security.
The time delay is particularly problematic. A released patch only protects systems on which it has actually been installed and activated. Even fully updated websites should check whether any suspicious activity occurred before the update.
Why was there a risk even before the publication?
Initial attack attempts were detected even before the official security update. Amazon recorded a targeted attack attempt against the PHP security vulnerability as early as October 17, 2026. This was four days before the official disclosure and release of the security updates.
In the days that followed, additional attack attempts were observed. This indicates that attackers may have already been aware of the vulnerabilities before website operators were notified.
Important: A documented attack attempt does not automatically mean that a website was successfully hacked.
Nevertheless, website operators should not only update their PHP version. They should also check whether their website was already attacked before the update.
Source: AWS Security
How can you check if your website is affected?
Step 1: Find out which version of PHP you're actually using
Open your hosting panel and look for the PHP setting for your domain. In WordPress, you can also find the version information under:
Tools → Site Health → Info → Server.
Important: The value displayed must correspond to the production website. A local test environment or the command line may use a different PHP version.
Step 2: Compare the version with the security updates
On October 21, 2026, the PHP project released these fixed versions:
Official PHP2Shell security updates
✓ Veröffentlicht| PHP branch | Minimum required version |
|---|---|
| PHP 8.5 | ✓8.5.12 |
| PHP 8.4 | ✓8.4.27 |
| PHP 8.3 | ✓8.3.36 |
| PHP 8.2 | ✓8.2.35 |
Therefore, ask your provider for a verified fix for both CVEs—not just the version number. In the medium term, you should switch to a supported PHP branch.
Step 3: Determine who is responsible for the PHP update
With shared hosting, the provider often handles package maintenance. With your own servers, VPS, or containers, this responsibility may fall to you.
Even having “automatic updates enabled” is not proof of a specific security fix.
Please ask your web host for the following four pieces of information:
- Which PHP runtime processes the requests for my domain?
- Have CVE-2026-109618 and CVE-2026-109619 been fixed?
- When was the fix installed, and were the PHP processes restarted?
- What other steps do you recommend for investigating past attacks?
Step 4: Update carefully, then test
First, create an externally stored backup and check your website's compatibility. Then install the appropriate PHP version or the confirmed provider update. Afterward, test contact forms, shop checkout, login, interfaces, and important pages.
A PHP security update is not the same as a WordPress core or plugin update. Both levels require their own maintenance. You can find support with technical adjustments through our web development services.
Step 5: Investigate suspicious activity
Check server-, PHP-, and access logs for unusual requests, unknown files, unexpected processes, or changes to user accounts.
Amazon recommends starting the PHP2Shell investigation from at least October 17, 2026. The absence of warnings does not prove that a server is clean.
If there are specific indications of a breach, you should consult an IT security expert, secure the affected systems, and update access credentials in a controlled manner. A standard website audit is not a substitute for a forensic security analysis.
What are the opportunities and risks involved in the remediation?
A quick update reduces the risk posed by these two known security vulnerabilities. Modern, supported PHP versions also make ongoing maintenance easier.
However, older themes, plugins, or custom developments may experience errors after a version change. That is why a backup and functionality testing are essential parts of the process.
A Web Application Firewall (WAF) can block known attack patterns. However, it does not replace the patch. Even temporarily disabling upload functions is only a limited protective measure.
If a critical system cannot be patched in a timely manner, you should evaluate its public accessibility together with your administrator.
How is the PHP security situation evolving?
The PHP2Shell cases demonstrate how quickly new attack patterns can emerge after a vulnerability is disclosed.
At the same time, security research is increasingly using AI tools to detect and analyze complex vulnerabilities. This accelerates the work of defenders, but it can also help attackers.
Also important is a separate report dated October 23, 2026: The PHP project described, under CVE-2026-115560, another attack vector that is relevant only in cases of unusual session configuration.
This announcement does not mean that the updates released on October 21 are ineffective against the original PHP2Shell vulnerabilities.
PHP temporarily recommends session.upload_progress.enabled=0 for the affected special configuration until a regular update is released.
Conclusion: What should you do now?
The PHP security vulnerability 2026 is real, critical, and relevant to many website operators. The appropriate updates for PHP2Shell have been available since October 21. However, security is only achieved once they have been applied to the PHP runtime you actually use.
Therefore, first check your version and, if necessary, request specific proof of the patch from your hosting provider. Then secure your website, test important functions, and check for suspicious activity from the period before the update.
To prepare for future incidents, it is important to have clear responsibilities, regular maintenance, and a transparent update process.
Do you want to review the technical foundation of your website and plan the necessary adjustments? Media Beats GmbH supports you with web development and website optimization. Contact us with no obligation.
FAQ
Our blog
Latest news
With our blog, you are always close to our work, our current projects and the latest trends and developments in web and print.
Any questions?





