Critical vulnerabilities discovered in PHP, the programming language behind around 70% of websites, are potentially putting businesses and internet users at risk.
Voldemaras Kadys, Head of Security & Platform Engineering at Mediatech, explains what these flaws mean for websites, how ordinary internet users could be affected, and why the release of security updates doesn’t necessarily mean websites are safe.
“PHP is a programming language that powers around 70% of all websites, including online services, stores, booking platforms, and many others. In other words, most websites you browse online are based on PHP and are therefore affected by the recent vulnerabilities.”
“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. The potential impact of these vulnerabilities may be huge, as most websites run on PHP.
“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.
“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.”
“For regular internet users, simply visiting a PHP website doesn’t necessarily mean their device will be compromised. The risk is that attackers may exploit a website that holds their personal information.
“For example, if a user has an account with an online shop, attackers may be able to hack that website through this PHP vulnerability and extract the information the user has stored there, such as their email address, physical address, name and date of birth.
“This kind of information may then be used for phishing, impersonation or other scams. However, not every PHP-powered website is vulnerable, and the vulnerability alone does not instantly mean a breach has happened.
“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.”
Gunnar Hellekson, vice president and general manager, Lightwell, Red Hat, said: “Much of the critical software running the world is also the least visible. Stable production code ‘that just works’ is now at risk due to the speed and volume of new vulnerabilities found via AI-driven discovery. The issues facing PHP are a reminder of just how deeply open source is woven into the systems that run global business.
“The ripple effects from vulnerabilities in foundational software like PHP can extend across entire industries. This makes it critical to have a trusted software source that helps manage this risk and, ideally, quickly responds to these new threats as they emerge.
“Given the potential impact of these vulnerabilities, Red Hat recommends that customers deploy validated, tested patches as soon as they are available from trusted sources, even outside of normal patching windows.”
Spencer Young, SVP International at global cybersecurity firm Delinea, believes alongside applying the security updates, organisations should be looking at whether attackers have already exploited the flaw and what the long-term risk could be.
“Organisations are racing to apply these emergency security updates before any damage is done. While essential, it’s only half the battle – they also need to check whether attackers have already been inside.
“If attackers have already exploited these weaknesses, they may have gained access to passwords or digital keys that could allow them back into the system, even after the flaws have been fixed. It means the security risk could still be there long after the immediate threat has been addressed and attackers could retain a way back in, waiting for another time to strike.
“If attackers have got in, the damage they could do depends partly on what they can reach. Getting into a website shouldn’t mean getting access to everything behind it. Limiting what each person or system can access helps stop one break-in spreading across an organisation.”
Donnan Mallon, threat intelligence analyst at Talion Cyber Security, said: “PHP has now confirmed it discovered evidence of one of the vulnerabilities in 2024 but could not find a way for a threat actor to attack a system using it. This meant the vulnerability was overlooked until August 2026 when it was disclosed to them by Calif.
“Organisations will undoubtedly want to understand why more was not done two years ago.
“We are now seeing evidence from Amazon’s threat team that attackers were working to exploit the vulnerabilities days before the public leak, but what we now need to understand is if attacks actually go much further back than this.
“The possibility that attackers had advance knowledge puts organisations in a far more dangerous position than they have been led to believe.
“Given this news, organisations must still focus on applying the patches, or taking sites offline, but they also need to monitor logs for evidence of historical compromise.
“This should now go back to 2024, which will add more pressure to security teams at a time when they are already completely overwhelmed.”
Samuel Hassine, CEO and co-founder, Filigran, said: “Taking a website offline for a day is a far cheaper decision than explaining a breach for a year. The agencies asking organisations to do exactly that are giving sound advice, and the speed of the coordinated response shows how much the discipline has matured.
“These flaws sat in code that dates back to 2004 and were found with AI. The same tools will help attackers move just as fast, and early attacks are already being reported.
“The job is simple to state and hard to do. Find every system running PHP, including the ones hidden inside third-party products. Update to a supported version or take it offline. Then check that nothing got in while the window was open. Patching is the easy part. Knowing what you run is the real test.”
Huntress recorded what normal PHP activity looks like across its customers before the patch dropped, so it can spot attacks fast now that the technical details are public.
What Huntress is telling businesses to do right now:
What’s changed since the leak: