For managers and business owners
Critical PHP flaw: what it means for your company website and what to do now
Two flaws in PHP let anyone take over a server without a password, and they are already being exploited. We explain, in plain language, whether your site is at risk and what to do today.
What happened
In the week of 20 October 2026, two serious flaws in PHP itself were disclosed, known as PHP2Shell (CVE-2026-109618 and CVE-2026-109619). They were found by researchers at Calif, with Wiz, OpenAI and Quarkslab[4]. The PHP team published the fixes on 21 October, a day earlier than planned, because the details were already circulating on social media[2].
Each is rated 9.2 on a scale of 10[2]. And since the 21st there have been records of real attacks trying to exploit them[2].
Why this is different from the usual flaws
Most security alerts concern one plugin or one specific program. Not this one. PHP is the language that makes the site work behind the scenes: it is used by more than 69% of websites whose server language is known[4], and in Portugal it runs 74.4% of .pt sites with identifiable technology[5]. A flaw in PHP is a flaw in all of them at once.
And it asks nothing of the victim. Nobody has to click a link, open an attachment or have a weak password: the site only has to be online with its server’s PHP unpatched[1].
What an attacker can do
A flaw like this gives whoever exploits it control of the server the site runs on. In practice:
- Steal data: customer contacts, quote requests, orders and logins stored on the site.
- Turn your domain against you: spread malware, send spam or host phishing pages under your company’s name, until Google and email providers start blocking it.
- Encrypt everything and demand a ransom: the site and the databases are locked until you pay (ransomware).
- Create a legal problem: a personal data breach can require you to notify the data protection authority within 72 hours under the GDPR (in Portugal, the CNPD).
Is my site affected?
If the site was built with WordPress, WooCommerce, PrestaShop, Joomla, Drupal, Magento or Laravel, it uses PHP and is probably exposed until shown otherwise. The flaws affect almost every version since PHP 5.4 and every way of serving PHP[1].
Updating WordPress, the theme or the plugins does not fix it. The flaw is in the server’s PHP, underneath all of that[7]. A site with WordPress up to date is still vulnerable if the server has not been updated.
In Portugal, exposure is high. Of the Portuguese servers that show their PHP version, most run old versions: 1,329 of 2,339 are on versions for which no fix exists at all, only replacement[5]. Universities, town councils and state bodies also have servers still to fix[6].
You can run a first check, free and risk-free, at nosis.pt/en/php-check. It reads only what your server shows publicly and never tests the flaw.
What to do today
- Ask whoever runs the site. Whether it is an agency, a technician or the hosting company, ask in writing for the PHP version on the server and confirmation that it has been updated.
- Update PHP to a fixed version and restart every PHP service. Without a restart, the old version keeps running[2]. The safe versions are 8.2.35, 8.3.36, 8.4.27 and 8.5.12 or later; PHP 8.1 and earlier have no official update and need a fix from the provider or a move to another version[2].
- If it cannot be updated yet, protect it. There are temporary measures that reduce the risk until the update is done, but they do not remove it[1].
- If none of that is possible quickly, consider taking the site offline until it is protected. That is the recommendation of the UK’s National Cyber Security Centre for systems that cannot be fixed in time[3].
- After fixing, confirm that nobody got in. Fixing closes the door, but does not tell you whether someone has already been through it.
What if the site is on shared hosting?
Then it is the provider that updates PHP. Many already have; others have not yet. The safest course is not to assume: ask for confirmation in writing. If the provider does not answer or cannot say, that is a good sign it is worth someone looking at the server.
Frequently asked questions
My site runs WordPress and is up to date. Am I protected?
Not necessarily. The flaw is in PHP, the language running underneath WordPress, not in WordPress, the plugins or the theme. A site with everything up to date is still exposed if the server’s PHP does not have the 21 October 2026 fix.
How do I know whether my site uses PHP?
If the site was built with WordPress, WooCommerce, PrestaShop, Joomla, Drupal, Magento or Laravel, it uses PHP. If in doubt, the free check at nosis.pt/en/php-check shows whether the server reveals signs of PHP, and your hosting provider can confirm the version.
An outside company does our hosting. Is this my problem?
The update is done by whoever runs the server, but the risk is your company’s: the customer data and the domain are yours. Ask the provider, in writing, to confirm that PHP has been updated to a fixed version and that the services have been restarted.
Should I take the site down?
Only if the server cannot be fixed or protected quickly. That is the recommendation of the UK’s National Cyber Security Centre (NCSC) for systems that cannot be updated or mitigated in time.
How do I know whether I have already been attacked?
There is no single sign. Changed files, new users in the admin panel, emails sent by the server for no reason or strange pages on the site are all clues. After fixing, it is worth asking whoever runs the server to look for signs of intrusion.
Sources
- CVE-2026-109618 and CVE-2026-109619: Critical Unauthenticated Remote Code Execution in PHP (Rapid7)
- PHP2Shell FAQ: CVE-2026-109618 & CVE-2026-109619 Fixes (watchTowr)
- Critical security issue affecting PHP (NCSC, UK)
- PHP2Shell: When PHP Runs Out of Memory at the Wrong Moment (Imperva)
- Exposição de Portugal ao PHP2SHELL: Em trinta segundos (Sérgio Silva, CyberS3c) (Tek Notícias)
- PHP2Shell: universidades, câmaras e Estado com servidores em versões (ainda) sem correção (João Tomé) (Tek Notícias)
- Tem um website em WordPress? Duas falhas críticas podem deixá-lo nas mãos de hackers, mesmo estando atualizado (Executive Digest)
Tell us which site. We'll tell you what to do.
Asking commits you to nothing: we reply first, and only go ahead with your agreement.
- 1We reply the same working dayWe confirm what you need and arrange the diagnosis.
- 2Full diagnosis: €150 + VATOn the server, with what we found and a fixed price for the fix.
- 3If you go ahead, the €150 is deductedYou only pay the difference.