PHP2Shell: What the October 2026 PHP Flaws Mean for Your Website
On 21 October 2026 the PHP project released emergency fixes for two critical security flaws, now known as PHP2Shell (CVE-2026-109618 and CVE-2026-109619). Both can let an attacker run code on a web server without logging in. The FBI's Cyber Division told organizations to update immediately, or take systems offline if they can't. If your website runs on PHP, and every WordPress site does, ask your host today whether it has been updated.
What happened
PHP is the programming language behind a large share of the web, including WordPress, WooCommerce, Joomla, Drupal and Magento. The PHP security team rated both flaws 9.2 out of 10 (CVSS v4.0) and released fixed versions: PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. The test release 8.6.0 RC4 includes the fixes too.
PHP's advice is blunt: updating is the only safe choice. Temporary workarounds close only some attack paths, and every PHP worker has to be restarted after the update for it to take effect.
Why the FBI got involved
The FBI's Cyber Division warned that the flaws could let attackers run code remotely in PHP itself. Its recommendations:
- Update PHP immediately. If that isn't possible, take the system offline until it's fixed
- List everywhere PHP runs, starting with anything facing the internet, including products that bundle PHP
- Watch servers for PHP processes that start command shells or download files
- If you suspect a break-in, isolate the system and report it to an FBI field office or the FBI's online complaint site
CISA, the US cyber-defense agency, also urged immediate patching, and news reports say agencies in Britain, Australia and Canada issued their own warnings.
Are attackers using it?
Reports conflict. Several security firms say they are seeing exploitation attempts at scale. When CISA published its alert, it said it had not observed exploitation yet, and some researchers report little beyond scanning. Either way, a flaw this severe gets attacked once the details are public, so treat it as urgent.
Is my website affected?
| Your site | Runs PHP? | What to do |
|---|---|---|
| WordPress or WooCommerce | Yes | Ask your host to confirm the PHP update and restart |
| Joomla, Drupal, Magento | Yes | Same as above |
| Custom site on shared hosting with a control panel | Often | Check the PHP version in the panel, or ask the host |
| Hosted builders such as Wix, Squarespace or Tilda | They run their own servers | Patching is their job; check their status page |
| Static site with no server code | No | Nothing to patch for this flaw |
How to check in five minutes
- If you log in at /wp-admin, your site is WordPress, which runs on PHP
- Page addresses ending in .php are a strong sign
- Your hosting control panel usually has a "PHP version" setting
- Ask your host: "Is PHP updated to 8.5.12, 8.4.27, 8.3.36 or 8.2.35, or patched by the vendor, and were the PHP workers restarted?"
- Or send us your address with the free PHP check ticked in the request form, and we'll tell you
If your site runs PHP
- Get PHP updated today, by you or your host, and make sure it's restarted
- Older versions 7.4 to 8.1 get no official release, only limited fixes from the PHP team; ask your host about patched packages or plan an upgrade
- Versions 5.4 to 7.3 are past end of life and get no fix at all
- Keep a recent backup somewhere separate from the server
- Look for warning signs: admin users you don't recognise, unfamiliar files, redirects to strange sites, warnings from your host
- If you suspect a break-in, take the site offline, restore from a clean backup and report it: in the US to the FBI, elsewhere to your national cyber emergency team
Why our sites aren't affected
The sites we build are fast static pages, or use a modern framework without PHP, so there is no PHP for this flaw to reach. When the advisory came out we still checked every client site. Services that a site connects to, such as form delivery, run on their providers' own servers and are patched by those providers.
Common questions
Is my WordPress site in danger?
WordPress runs on PHP, so it is exposed until your host updates PHP to a fixed version and restarts it. Many managed WordPress hosts do this for you, but ask yours to confirm.
Do I need to change my website?
Not necessarily. Updating PHP closes these two flaws. Moving to a site without PHP removes this whole class of risk, which is worth considering if your site is rarely updated.
Are sites on Wix, Squarespace or Tilda affected?
Those platforms run their own servers, so patching is their responsibility. Check their status pages if you're worried.
Sources
- PHP: Critical remote code execution vulnerabilities, update now (21 Oct 2026)
- FBI Cyber Division: PHP vulnerabilities warning (21 Oct 2026)
- MeriTalk: CISA urges immediate patching of critical PHP flaws
- Tenable: PHP2Shell frequently asked questions
- Ubuntu: PHP2Shell fixes available
- CyberScoop: PHP releases emergency fixes for 2 critical vulnerabilities
Your site could be next on screen.
See your prices, pick a package, and send us a request.