Is your website being looked after?
Ten seconds to see what your site runs on, who hosts it, and what needs attention, including this week's PHP2Shell flaw.
PHP2Shell, in plain terms.
What happened
On October 21, PHP fixed two serious flaws. PHP runs behind most small business sites, including every WordPress site.
What's at risk
An attacker could take over the server with no password. That reaches your site, form messages and stored passwords.
What fixes it
A PHP update on the server, usually your host's job. Updating WordPress or switching themes won't fix it.
Where the big hosts stand
From each host's own announcement. Updated Oct 22.Many hosts apply the fix without changing the PHP version number. Builders like Squarespace and Wix aren't affected.
Think you've been hacked?
- Leave the files alone, so there's a trail to clean up.
- Tell your hosting company today.
- Change your hosting, website and email passwords.
Then run the check and ask for a free review.
What your web person should handle
- Monthly updates, with a backup first
- PHP on version 8.3 or newer
- Backups kept off the website's server
- Watching for downtime and hacks
- Domain and certificate renewals
- Accounts in your name, with your login
Questions.
Is it safe to run this on my site?
Does a clean result mean my site is secure?
Should I move to Squarespace, Wix or Shopify?
What do you do with the website I enter?
This check looks at public information only and can't guarantee a website is secure. PHP2Shell is tracked as CVE-2026-109618 and CVE-2026-109619.