What is the PHP security alert?
PHP has released fixes for two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619. Both can allow unauthenticated remote code execution. PHP says all installations serving web requests are at risk, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed. It considers the demonstrated risk highest for mod_php.
The fixed releases are PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. The correct version depends on the supported branch already used by your server. Do not change the runtime blindly: ask the hosting provider or developer responsible for compatibility, backups, deployment and testing to install the applicable vendor package.
Amazon Threat Intelligence says it observed an exploitation attempt on 17 October, before public disclosure, and additional attempts from multiple actors on 21 October. It now describes PHP2Shell as broadly exploited in the wild. Its sensors do not prove that any particular merchant website has been attacked or compromised.
Ask your hosting provider to update PHP now
WooCommerce, Adobe Commerce, OpenCart, PrestaShop and many custom shops depend on PHP. Updating a theme or payment plugin does not update the server runtime. Send your host the official PHP advisory and ask which PHP branch each internet-facing application uses, when the patched package will be installed, and how service will be tested afterwards.
PHP 8.1 and older no longer receive normal releases from the PHP project. Some Linux distributions and long-term-support vendors may supply backported fixes, and PHP has published minimal source backports for 7.4, 8.0 and 8.1. Ask your vendor what is actually covered and plan a move to a supported branch rather than assuming an old installation is safe.
PHP says temporary measures reduce particular attack paths but do not make an installation safe; updating is the complete solution. The NCSC advises considering taking systems offline where immediate remediation is not feasible. Let the host or security professional make server-configuration decisions.
On 22 October, a UK technology minister told the House of Lords that 32 government services were unavailable and four were partially unavailable, largely because of precautionary measures while security updates and mitigations were applied. That does not establish that those services, or any particular merchant, were compromised; it does show why a controlled maintenance window can be the safer operational choice. Later, NCSC chief technology officer Ollie Whitehouse said there were no indications that the flaw had been successfully exploited against UK government systems.
Also check WooCommerce and WooPayments
WooCommerce released core version 11.2.2 on 4 November as a security release with multiple security updates. It covers Store API checkout, REST API authentication, admin connection endpoints, payment-profile data and product import validation. WooCommerce says the release also needs a database update and recommends updating as soon as possible.
WooPayments issued a separate security update on 3 November for subscriptions functionality bundled with the payment plugin. The current release is 11.2.1, but WooCommerce also lists fixed releases for older version lines. Updating WooCommerce core does not confirm WooPayments is current, and updating WooPayments does not patch the PHP runtime.
Before changing production, record both plugin versions and take a current backup using your normal host or developer process. Update WooCommerce core, complete its database update, then update WooPayments to the fixed release for the installed version line. Confirm each installed version after the update.
Place a low-value test order through the same checkout customers use. Check the basket, shipping, tax and total; confirm the order is saved once; verify the payment reaches a clear result; and match the transaction reference in WooCommerce. WooCommerce notes that Store API checkout now returns an HTTP 500 response if certain extension callbacks fail while the order is being saved. Give your developer the timestamp, order ID, payment method and error log, never card numbers or security codes.
The official notices do not give a CVE number, severity score or evidence of exploitation for these particular plugin updates. They do not identify a live WooCommerce-wide outage. Do not present a merchant’s failed checkout as caused by PHP, WooCommerce or WooPayments without server logs or a confirmed provider finding.
Website offline? Keep a separate way to pay
A standalone card machine takes payments through its payment service, rather than your shop’s PHP checkout. For customers visiting your premises or collecting an order, use the terminal you already have and record the sale against the order. Check its connection and the payment result as usual.
For remote orders, takepayments offers payment links that work without a website. Create the link through the provider’s service and share it with the customer. The customer enters payment details on the provider-hosted payment page, rather than your shop. Use an existing approved service, with staff who know how to use it.
For a click-and-collect order, agree the item and collection time, take payment through that separate route, then match the payment to the order reference. Confirm the result before fulfilment or another payment attempt. The fallback needs its own working service and connection; it does not repair the website.
Choose a payment setup beyond your checkout
Want a card machine for your counter and payment links for remote customers? Get a quote built around how you sell, the equipment you need and your payment volumes. Ask for the complete fees and contract terms together, including any separate service charges.
Awais can talk through the payment options while your host handles the PHP work. One clear plan for the website, another for taking orders: customers know how to pay, and your team knows where to find the transaction.
Common questions
Does the PHP update also update WooCommerce?
No. PHP is the server runtime. WooCommerce core and WooPayments are separate WordPress plugins. Check and update each layer independently.
Do the November WooCommerce notices explain failed online payments?
Not by themselves. The notices do not identify a live outage or prove that a particular store was attacked. Use site logs, provider status records and a controlled checkout test to establish the cause.
Sources and dates
Checked 22 Oct 2026, 14:40 UK time
Checked 21 Oct 2026, 13:11 UK time
Checked 19 Nov 2026, 13:40 UK time
Checked 21 Oct 2026, 13:11 UK time
Checked 21 Oct 2026, 13:11 UK time
Checked 21 Oct 2026, 13:11 UK time
Checked 21 Oct 2026, 13:11 UK time
Checked 21 Oct 2026, 13:11 UK time
Checked 21 Oct 2026, 13:11 UK time
Checked 21 Oct 2026, 13:11 UK time
Checked 22 Oct 2026, 14:40 UK time
Checked 22 Oct 2026, 19:19 UK time · Published 2026-10-22
Checked 19 Nov 2026, 13:58 UK time · Published 2026-11-04
Checked 19 Nov 2026, 13:58 UK time · Published 2026-11-03
Checked 5 Nov 2026, 15:07 UK time
Update log
- . Rechecked the PHP and NCSC notice confirming the October release. The hosting team can confirm which update its live checkout received.
- . Updated at 15:07 GMT on 5 November after WooCommerce published separate security updates for WooPayments on 3 November and WooCommerce core 11.2.2 on 4 November. Added version checks, database-update and checkout-test steps, and the evidence limit that the notices do not establish a live outage or the cause of an individual failed checkout.
- . Updated at 19:19 BST on 22 October to add the later NCSC position that there were no indications the PHP flaw had been successfully exploited against UK government systems. The reported disruption to government services was largely precautionary while fixes and mitigations were applied.
- . Updated at 14:40 BST on 22 October after Amazon Threat Intelligence reported exploitation attempts from 17 October and said PHP2Shell is now being broadly exploited in the wild. The advisory also reflects the patched releases, confirmed affected scope, incomplete temporary mitigations and the UK government's report that 32 services were unavailable and four partially unavailable, largely as a precaution while fixes were applied.
- . Published with the official pre-release status checked at 13:11 UK time. Fixed version numbers and reported attacks omitted because they were not confirmed in the official sources checked.
