All news

23 October 2026 / 6 minutes of reading

You've Updated PHP. But Is Your Website Really Secure?

Security patches for two critical PHP vulnerabilities are now available. But installing them doesn't necessarily mean the problem is over. Here's what your business should check after updating PHP, and when a more thorough security assessment may be needed.


Updating PHP is one of the most important steps businesses can take to protect their websites and applications against recently discovered critical vulnerabilities. However, if an attacker gained access to a server before the security patch was installed, the update won't necessarily undo the damage. Malicious files, unauthorized access or other changes may remain, potentially allowing the attacker to continue operating even after the vulnerability has been fixed.

Installing a security patch doesn't prove that your system hasn't already been compromised. When dealing with serious vulnerabilities, it's important to assess not only the server's current security but also, depending on the level of risk, what may have happened before the update.

Why Are These PHP Vulnerabilities So Serious?

PHP powers a large number of business websites, online stores, customer portals and internal applications. In October 2026, two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619, were disclosed. Under certain conditions, they could allow attackers to run malicious code on a server remotely, without needing to log in.

The problem isn't with a particular website or plugin. It lies within PHP itself. This means even applications running an up-to-date content management system, with properly configured user permissions and no known flaws in their own code, could be at risk. The actual level of exposure depends on the PHP version, server configuration and other factors. A successful attack, however, could lead to unauthorized access, data theft or disruption of services.

For a deeper technical explanation of the vulnerabilities, how they can be exploited and what security researchers have discovered, read our article PHP2Shell: Two Critical PHP Vulnerabilities Threaten the Security of Entire Servers.

How Can You Tell If Your Business Is Affected?

The first step is to identify every system in your organization that uses PHP. Beyond your main company website, this could include an online store, customer portal, internal application or older system managed by an external provider. Testing environments and containers also deserve attention, as they aren't always included in routine update processes.

It's important to distinguish between updating a web application and updating the PHP software running on its server. For example, having the latest version of WordPress doesn't automatically mean the server is running a patched version of PHP. If an external agency or hosting provider manages your website, ask them to confirm that the relevant security patches have been applied across all affected environments and that the updated PHP version is actually running in production.

For older PHP versions, you'll also need to check whether your software vendor provides security fixes. Some Linux distributions apply security patches without changing the main version number, so the version displayed doesn't always tell the full story.

What Should You Check After Updating PHP?

Applying a patch fixes the specific vulnerability, but it doesn't tell you whether someone tried to exploit it before the update. Depending on how critical the system is, your security checks should therefore cover the period before the patch was installed, not just its current state.

A good starting point is to review the available logs from the web server, application and operating system. Security teams should look for unusual HTTP requests, unexpected errors while processing requests, PHP process crashes or suspicious connections between the server and external systems. None of these events necessarily proves an attack took place, but they may point to activity that warrants further investigation.

It's equally important to check whether files or server settings have been changed without authorization. An attacker who gained access may have created new files, modified existing scripts, changed permissions or established another way to get back into the system. In that situation, they may no longer need the original PHP vulnerability to maintain access. Fixing it alone won't remove the consequences of the attack.

If the application handles personal data, login credentials or sensitive business information, the assessment should also consider whether any of that information may have been accessed. A confirmed incident may require more than restoring the system: there could also be legal or contractual obligations to address.

Even if you find no obvious signs of suspicious activity, that doesn't necessarily mean the system was never compromised. The reliability of a retrospective investigation depends on which logs were collected, how long they've been retained and whether they may have been altered during an attack.

When Is a More Thorough Security Assessment Needed?

Not every vulnerability calls for a full-scale investigation. The right response depends on whether the system was actually vulnerable, how long it was exposed, what data it processes and whether there are signs of exploitation. An internal testing application that isn't accessible from the internet presents a different level of risk from a public-facing customer portal handling personal information.

If there's reason to believe an attacker has already exploited the vulnerability, the priority is to investigate the incident. The goal is to establish whether unauthorized access occurred, what the attacker did, which systems or data may have been affected and what needs to be done to contain and recover from the attack. This may involve examining system logs, processes, files and other digital evidence.

Penetration testing serves a different purpose. Security experts simulate real-world attacks to identify weaknesses in web applications and infrastructure that could still be exploited. These might include authentication flaws, excessive permissions, poorly secured APIs or risky server configurations. Penetration testing helps organizations understand how resilient their systems are against future attacks, but it doesn't replace an investigation into an incident that may already have happened.

The key is to understand what you're trying to establish. If you suspect a breach, you first need to investigate what happened and address the consequences. If your goal is to assess your application's overall security and uncover other exploitable weaknesses, penetration testing is the appropriate approach.

Security Doesn't End With a Software Update

The recent PHP vulnerabilities highlight why businesses shouldn't rely on updates as their only line of defense. Similar security flaws can emerge in operating systems, databases, web servers and other technologies that business services depend on.

Organizations need an up-to-date inventory of the software they use, clear ownership of maintenance and updates, and the ability to respond quickly when new security warnings are issued. Keeping relevant security logs, monitoring suspicious activity and regularly assessing the security of applications and infrastructure are equally important.

Updating PHP is essential, but protecting your systems also means checking whether they were compromised before the patch was applied. Only then can a business gain a clearer picture of its exposure and decide whether further action is necessary.

logo

Sign up for our newsletter for all the important cybersecurity and ethical hacking news.

© 2026 citadelo AG. All rights reserved.

facebooklinkedinxyoutube