Two flaws in PHP, the language behind WordPress, WooCommerce, Magento and Drupal, let outsiders take over the server that runs a website. Attackers are using both. Make sure whoever runs your site updates PHP this week.
- 01If someone gets in, they can usually reach whatever your website can: customer data, your checkout and connected systems.
- 02Magento and Adobe Commerce 2.4.4 and 2.4.5 stores run only on PHP 8.1, which gets no fix. They need a platform upgrade first.
- 03In India, CERT-In requires companies to report listed incidents, including website intrusions and data breaches, within 6 hours of noticing them. Decide now who makes that call.
In plain words
- PHP
- The programming language behind WordPress, WooCommerce, Magento and Drupal, and 69.2% of websites whose server language is known (W3Techs, 30 October 2026).
- Server
- The computer, usually rented from a hosting company, that runs your website and stores its data.
- Fix (update)
- A new version of the software that closes the flaw.
- Web application firewall
- A filter in front of your website that blocks some suspicious traffic. CISA says it may help until systems are fixed.
- CISA
- The US government’s cyber security agency. It keeps a list of flaws that attackers are known to be using.
- CERT-In
- India’s national agency for responding to cyber security incidents.
Attackers are using two PHP flaws
On 21 October 2026 the PHP project disclosed two flaws that let an outsider take over the server behind a PHP website, with no password. Five days later CISA, the US government's cyber security agency, listed both as being used by attackers. It gave US federal agencies until 29 October to fix them. CISA's alert calls the pair php2shell. PHP is the programming language behind WordPress, WooCommerce, Magento and Drupal. W3Techs, which surveys the web, says 69.2% of websites whose server language it can identify use PHP. See sources 1–5.
Why two PHP flaws reach so many websites
- of websites whose server language is known run on PHP
- 69.2%
- of all websites run on WordPress, which needs PHP
- 39.5%
WordPress, WooCommerce, Magento and Drupal all run on PHP
If your site runs on one of these platforms, it runs on PHP. WordPress alone runs 39.5% of all websites, according to W3Techs, and it requires PHP. So does WooCommerce, the store add-on for WordPress. Magento, Adobe Commerce and Drupal list PHP in their own requirements too. The PHP project and CISA do not name these platforms. The link comes from the platforms needing PHP to run. Noesis analysis: on a fully hosted service, where the vendor runs the servers, the fix is the vendor's job. Ask them to confirm it in writing. See sources 6–10.
Which platforms depend on PHP
| Aspect | Needs PHP? | Who applies the fix? |
|---|---|---|
| WordPress | Yes | Your host or developer |
| WooCommerce | Yes, through WordPress | Your host or developer |
| Magento and Adobe Commerce | Yes | Your host or developer |
| Drupal | Yes | Your host or developer |
| Fully hosted service | Ask your vendor | The vendor, once they confirm it |
An attacker gets what your website can reach
The PHP project confirms that an outsider can run their own instructions with the same access as your website. Noesis analysis: whatever your website can reach, an attacker in that position can usually reach too. For a typical business site, that covers five things.
- Customer records, such as names, addresses, phone numbers and order history in the site's database.
- The checkout, where hidden code can copy card details as customers type them.
- Admin access, since new administrator logins let an attacker stay in after the flaw is fixed.
- Connected systems, because sites often store passwords or keys for payment, CRM, ERP and email services.
- The brand, as pages can be changed, visitors sent to scams, or your domain used to send spam.
What sits behind a typical website
Your customers
- Names and addresses
- Order history
- Account logins
Your revenue
- Checkout pages
- Payment provider keys
Your operations
- CRM and ERP connections
- Email sending
- Admin accounts
Your brand
- Home page
- Domain and email reputation
Downtime, lost sales and reporting cost more than the fix
Noesis analysis: the fix itself is rarely the expensive part. The cost is the days a store is offline and the sales lost while it is down. It is the customers who may need to be told their data was exposed, and the trust that is slow to rebuild. There is also a reporting duty. In India, CERT-In's 2022 directions require companies to report listed cyber incidents within 6 hours of noticing them. The list includes website intrusions that insert malicious code, data breaches, and attacks on e-commerce and digital payment systems. This is not legal advice, so check your own obligations. Noesis recommendation: the founder or business head should own the decision to report. CISA records the flaws' use in ransomware as unknown. See sources 4, 5 and 12.
Magento 2.4.4 and 2.4.5 stores cannot simply update
For a current site, updating PHP is routine work. For older sites it is harder. CISA says PHP 8.1 and earlier are unsupported and get no fix. It advises taking such systems offline until they are upgraded. Adobe lists Magento and Adobe Commerce versions 2.4.4 and 2.4.5 as supporting only PHP 8.1. Stores on those versions need a platform upgrade first, which takes planning and testing. Noesis recommendation: if this is you, ask for an upgrade plan with dates now. Ask what will protect the store until then. CISA says a web application firewall may give some protection until systems are fixed. See sources 4 and 9.
Five questions for your developer this week
Your job is to get answers to these questions from whoever runs your website: your agency, your developer or your host. The first three steps follow CISA's guidance. The rest are Noesis recommendations.
- Which of our sites and systems use PHP? Include ones that are easy to forget, such as microsites, blogs, old campaign pages and internal tools.
- Has each one been updated to a fixed version of PHP?
- What cannot be updated this week? Agree a date and a stopgap for each, or take it offline as CISA advises.
- Have you checked for signs of misuse, such as unfamiliar admin accounts, changed checkout pages or unexpected files?
- Who decides whether we report an incident, and to whom?
Five answers to get this week
- 01Which sites and systems use PHP?Pass when: A complete list, including forgotten microsites and tools
- 02Is each one updated?Pass when: Each site is on a fixed version of PHP
- 03What cannot be updated yet?Pass when: Each has a date and a stopgap, or is offline
- 04Any signs of misuse?Pass when: Admin accounts, checkout pages and files have been reviewed
- 05Who reports an incident?Pass when: A named person knows what to report, and to whom
An update does not prove nobody got in
Do not assume your site was attacked because it ran an older version. Equally, do not assume it is safe because it has since been updated. A fix closes the door; it does not show whether someone came in earlier. Do not rely on headlines about scale. The official sources do not say how many sites were affected. And do not assume a hosted platform is covered until the vendor confirms it. We have not tested any system against these flaws.
For your technical team.
Forward this section. Fixed releases: PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. The advisories are dated 21 October; php.net's changelog lists 8.5.12 and 8.4.27 on 22 October (release dates differ). CVE-2026-109618 and CVE-2026-109619 each carry a CVSS v4 score of 9.2. Remote code execution without a login was validated over HTTP against mod_php with default PHP input and memory limits. The first advisory judges PHP-FPM, FrankenPHP and LSAPI likely susceptible but unproven. CISA's alert covers all PHP installations serving web requests, including php-cgi and LiteSpeed, and publishes a SIGMA detection rule. Look for PHP worker processes launching shells or downloading tools. Interim settings such as session.upload_progress.enabled=0 reduce exposure, but the advisories say only upgrading is a complete fix. See sources 2–5 and 11.
Sources & context
Sources checked 2026-10-31. Recommendations and illustrative scenarios are Noesis’s analysis, not claims of client results.
- 1 / W3Techs — Usage statistics of PHP for websites; daily survey, figures for 30 October 2026; accessed 31 October 2026 ↗
- 2 / PHP project — GitHub advisory GHSA-w8hw-w9fx-j79w (CVE-2026-109618); published 21 October 2026; accessed 31 October 2026 ↗
- 3 / PHP project — GitHub advisory GHSA-6wmf-4rv5-p3rp (CVE-2026-109619); published 21 October 2026; accessed 30 October 2026 ↗
- 4 / CISA — Critical Vulnerabilities in PHP Require Immediate Patching; alert dated 21 October 2026, last revised 26 October; accessed 31 October 2026 ↗
- 5 / CISA — Known Exploited Vulnerabilities catalogue; both flaws added 26 October 2026, federal due date 29 October; accessed 30 October 2026 ↗
- 6 / W3Techs — Usage statistics of WordPress; figures for 30 October 2026; accessed 31 October 2026 ↗
- 7 / WordPress.org — Requirements; last modified 7 May 2026; accessed 31 October 2026 ↗
- 8 / WooCommerce — Server requirements; page date not stated; accessed 31 October 2026 ↗
- 9 / Adobe — Adobe Commerce and Magento Open Source system requirements; last updated 13 October 2026; accessed 31 October 2026 ↗
- 10 / Drupal.org — PHP requirements; last updated 4 August 2026; accessed 31 October 2026 ↗
- 11 / php.net — PHP 8 ChangeLog; 8.5.12 and 8.4.27 dated 22 October 2026; accessed 30 October 2026 ↗
- 12 / CERT-In — Directions under section 70B(6) of the IT Act, 2000; dated 28 April 2022; accessed 31 October 2026 ↗
