Enterprise IT World
Features Security

Critical PHP Vulnerabilities Put Websites and Customer Data at Risk

Voldemaras Kadys

With PHP powering around 70% of websites globally, two critical security flaws highlight the risks of unpatched infrastructure, potential data theft and the responsibility of website operators to act swiftly.

Two critical security vulnerabilities discovered in PHP, one of the world’s most widely used programming languages, have raised concerns about the security of websites, online services and the personal information they hold. With PHP estimated to power around 70% of websites globally, the flaws highlight how weaknesses in widely deployed software can create risks extending far beyond individual organisations.

The vulnerabilities could potentially allow attackers to execute malicious code on affected servers, take control of vulnerable systems and compromise the websites running on them. Depending on the permissions available to an attacker, the consequences could include the theft of customer information, unauthorised changes to website content, malware installation or disruption of online services.

PHP developers have released security updates to address the flaws. However, the availability of a fix does not automatically make websites secure. Operators and hosting providers must identify affected systems, install the appropriate updates and verify that their environments are protected.

The incident highlights a persistent challenge in cybersecurity: vulnerabilities in widely used technologies can have a substantial potential impact, but the speed and effectiveness of remediation ultimately depend on the organisations responsible for maintaining those technologies.

Why PHP’s Security Matters

PHP, originally known as Personal Home Page and now commonly referred to as PHP: Hypertext Preprocessor, is a server-side programming language used to develop and operate dynamic websites and web applications.

Unlike technologies that primarily run within a visitor’s browser, PHP typically processes requests on a web server. It can retrieve information from databases, manage user sessions, process online transactions and generate the content delivered to visitors.

The technology supports a broad range of online services, including e-commerce platforms, booking systems, content management systems, business portals and other applications that rely on server-side processing.

“PHP is a programming language that powers around 70% of all websites, including online services, stores, booking platforms, and many others,” says Voldemaras Kadys, Head of Security & Platform Engineering at Mediatech. “In other words, most websites you browse online are based on PHP and are therefore affected by the recent vulnerabilities.”

While the widespread adoption of PHP makes the vulnerabilities significant, the distinction between the number of websites using the language and the number actually vulnerable is important. Not every PHP-powered website is necessarily exposed. The level of risk depends on factors such as the PHP version in use, the server configuration, the availability of security fixes and whether the affected code paths can be reached by an attacker.

Nevertheless, the extensive use of PHP means that identifying and securing affected installations is an important task for organisations operating online services.

Two Critical Flaws Raise the Stakes

The two vulnerabilities were classified as critical because they could potentially enable attackers to compromise vulnerable website servers. Successful exploitation could give an attacker the ability to execute unauthorised commands or code, depending on the circumstances and privileges of the affected environment.

“The two critical security flaws were discovered in PHP that could allow hackers to take control of vulnerable website servers and potentially steal customer information, change website content, install malware or take the website completely offline,” Kadys explains.

The consequences could vary considerably between organisations. In a relatively limited incident, an attacker might alter a webpage or disrupt a particular service. In a more serious compromise, access to the server could provide an opportunity to obtain sensitive information, interfere with application operations or establish a foothold for further attacks.

For an online retailer, this could mean exposure of customer records or disruption of its shopping platform. For a booking provider, it could affect reservations and customer account information. For a business portal, the impact might extend to confidential information or the availability of services used by employees and customers.

The extent of any compromise would depend on the affected application, its security controls, the permissions granted to the vulnerable process and the attacker’s ability to move beyond the initially compromised component.

A critical vulnerability does not, by itself, establish that attackers have exploited a particular website or that customer data has been stolen. It indicates that the underlying weakness could have serious consequences if the conditions for exploitation are present.

However, the potential impact is substantial when the vulnerable technology is used across such a large portion of the internet.

A Security Patch Does Not Guarantee Protection

PHP developers have released updates to address the vulnerabilities, giving administrators a route to remediate affected systems. The challenge is ensuring that those updates are installed across the many environments where PHP operates.

Unlike a centrally managed service in which a provider can deploy a fix to every customer simultaneously, PHP installations may be maintained by individual businesses, hosting companies, application vendors and managed service providers. Some organisations maintain their own infrastructure, while others depend on third parties to manage the underlying software.

This fragmented responsibility can slow remediation.

An organisation may be unaware that an older PHP version is still running on a production server. A hosting provider may manage the runtime, while the website owner controls the application. In other cases, a legacy business application may depend on an older version that has not been tested against newer releases.

“PHP developers have already issued updates for these vulnerabilities, but that doesn’t mean all websites are automatically safe – website operators and hosting providers need to install the updates themselves, and hopefully they do that as soon as possible,” Kadys says.

The gap between a vulnerability’s disclosure and the installation of a fix is particularly important when the affected software is publicly accessible. Attackers can examine vulnerable software, study security advisories and develop methods to identify systems that have not been updated.

Consequently, organisations should not assume that making a patch available is sufficient. They need to establish which systems are affected, prioritise internet-facing installations, apply the appropriate updates and confirm that the remediation has been successful.

Security teams should also review whether vulnerable systems were exposed before the patch was installed. Updating software closes a known weakness, but it does not automatically remove malicious files, reverse unauthorised changes or eliminate access that an attacker may already have established.

Why End-of-Life PHP Versions Are a Concern

One particularly important aspect of the incident is the release of security updates for PHP versions that have reached end of life.

End-of-life software no longer receives routine support and typically does not receive further security fixes. Organisations that continue using such versions therefore face a growing maintenance challenge as newly discovered vulnerabilities emerge.

Kadys points to the decision to issue updates for end-of-life PHP versions as an indication of the seriousness of the vulnerabilities.

“The seriousness of the vulnerabilities is also evident from the fact that PHP released updates even for End-Of-Life (EOL) PHP versions, which are no longer actively supported and typically do not receive any more updates,” he says.

Although an exceptional security release can help organisations operating older installations, it should not be treated as a substitute for upgrading to a supported version.

Legacy systems often remain in production because they support business-critical applications, depend on older libraries or require extensive testing before an upgrade can be completed. In some cases, organisations may be reluctant to change a working environment because of the possibility of operational disruption.

Yet maintaining unsupported software creates an ongoing exposure that cannot always be addressed through routine patching.

Organisations should therefore use the incident as an opportunity to review their software inventories, identify unsupported PHP installations and develop migration plans. Where an immediate upgrade is not possible, compensating controls, restricted network access and additional monitoring can help reduce exposure while a longer-term solution is implemented.

What Does This Mean for Ordinary Internet Users?

For internet users, the immediate concern is not necessarily that visiting a PHP-powered website will infect their devices. The more direct risk is that attackers could compromise a website holding their personal information.

“For regular internet users, simply visiting a PHP website doesn’t necessarily mean their device will be compromised,” Kadys says. “The risk is that attackers may exploit a website that holds their personal information.”

Consider an online shopping account. If the underlying website is vulnerable and an attacker successfully compromises its server, the attacker might be able to access information stored by the service, depending on the extent of the breach and the application’s security architecture.

That information could include names, email addresses, physical addresses and dates of birth. Depending on the service and the nature of the compromise, other information could also be at risk.

Such data can be valuable to criminals even when passwords or payment information are not exposed. Names and contact details can make fraudulent messages more convincing, while addresses and other personal details can help criminals impersonate legitimate businesses or individuals.

Kadys warns that stolen information could subsequently be used for phishing, impersonation and other scams.

However, the vulnerability alone does not establish that any particular user’s information has been stolen. Nor does it mean that every website built with PHP is vulnerable. The actual exposure depends on the software version, configuration, security controls and whether exploitation has occurred.

“The release of a security update does not mean every website is safe. Website operators and hosting providers must install the fixes themselves, and any delay could leave vulnerable systems exposed to attackers.”

— Voldemaras Kadys, Head of Security & Platform Engineering, Mediatech

For consumers, the appropriate response is vigilance rather than abandoning online services.

“There’s no reason to stop browsing or shopping online, but users should still be extra cautious about suspicious messages because we don’t know what kind of data hackers may have stolen through this vulnerability, and from which websites,” Kadys says.

Users should be wary of unexpected emails or text messages requesting personal information, encouraging urgent account verification or directing them to unfamiliar login pages. They should access services through their usual official websites or applications rather than following suspicious links.

Where a service confirms that customer information has been exposed, users should follow its guidance, change affected passwords and enable multifactor authentication where available. Reusing passwords across multiple services should also be avoided, as credentials compromised on one platform can put other accounts at risk.

What Organisations Should Do Next

For businesses, the PHP vulnerabilities reinforce the importance of treating patch management as an operational security responsibility rather than an occasional maintenance exercise.

The first step is to establish where PHP is running. Organisations should review server inventories, cloud environments, containers, hosting arrangements and applications maintained by third-party providers. Older systems and internet-facing services deserve particular attention.

They should then determine which versions are affected and apply the relevant security updates in accordance with the official PHP advisories. Organisations using managed hosting should confirm with their providers that the appropriate fixes have been applied rather than assuming that the provider has already taken action.

After patching, administrators should verify the installed versions and assess whether additional remediation is required. This includes reviewing server logs for suspicious activity, checking for unexpected changes to application files and investigating unusual access patterns.

If there is evidence of a compromise, patching alone may not be sufficient. Incident responders may need to isolate affected systems, revoke exposed credentials, remove malicious components, restore clean systems and determine whether customer or business information has been accessed.

Organisations should also review their dependency management and upgrade processes to reduce reliance on unsupported software. Regular vulnerability scanning, clearly defined patching responsibilities and timely communication between website owners and hosting providers can help prevent similar exposure in the future.

A Reminder About the Internet’s Shared Infrastructure

The PHP vulnerabilities illustrate how a weakness in a widely deployed technology can create security implications for businesses and consumers across multiple sectors.

They also highlight the difference between identifying a vulnerability and eliminating the resulting risk. Security researchers and software maintainers can discover flaws and release fixes, but effective protection depends on how quickly those fixes reach production systems and whether organisations can identify signs of previous compromise.

For businesses, the priority is to determine their exposure, patch affected installations and investigate any indications of malicious activity. For users, sensible online security practices and caution around unexpected communications remain important.

Ultimately, the security of widely used software depends on a shared responsibility among developers, hosting providers, website operators and users. The release of a patch is an essential first step, but the work is not complete until vulnerable systems have been secured and any evidence of exploitation has been addressed.

Related posts

From Data Lakehouses to AI Agents: Building an Enterprise Data Foundation That Scales

enterpriseitworld

Fortinet and Equinix Join Forces to Secure Distributed AI Environments

enterpriseitworld

Reimagining Healthcare: The Digital Hospital of Tomorrow

enterpriseitworld