NSA warned this morning about two critical PHP flaws that let attackers into your server's files and database. If you run WordPress or anything else on PHP, paste this prompt into Claude Code and it will check every site you own in a few minutes, without changing anything. 𝗣𝗿𝗼𝗺𝗽𝘁: "PHP released emergency security fixes on Oct 21, 2026 for two critical flaws, CVE-2026-109618 and CVE-2026-109619 (CVSS v4.0 9.2). They allow unauthenticated remote code execution on any PHP install that serves web requests (PHP-FPM, mod_php, php-cgi, FrankenPHP, LiteSpeed). Fixed versions: PHP 8.5.12, 8.4.27, 8.3.36, 8.2.35. PHP 8.1 and older get no official release, though PHP published source backports for 7.4, 8.0 and 8.1 and some distros/LTS vendors backport fixes. NSA and the UK NCSC advise patching now or taking unpatchable systems offline. Help me check whether any of my sites are exposed. Work read-only, and do not change, patch, restart or delete anything without asking me first. 1. Search the web for the latest php.net advisory, NSA, CISA and NCSC guidance on these two CVEs, including whether they're being exploited in the wild. Tell me if anything above is out of date. 2. Ask me for the list of my domains, hosting accounts and servers. Also ask about anything I might have forgotten: old WordPress installs, staging sites, parked domains, client sites, and old hosting plans I still pay for. 3. For each domain, find out where it is hosted and whether it runs PHP. Check DNS, the response headers (Server, X-Powered-By, cookies like PHPSESSID) and common PHP or WordPress paths such as /wp-login.php, /xmlrpc.php and /index.php. Only send normal requests to sites I own. Do not try to exploit anything. Headers often hide the version, so mark those as unsure rather than guessing. 4. For any server I can reach over SSH or a hosting panel, tell me how to check the exact PHP version (php -v, or the panel's PHP settings). If PHP comes from a distro or vendor package (Ubuntu, Debian, RHEL, cPanel EA-PHP, etc.), the version number may not change after patching, so also check the package changelog or the vendor's security advisory for these CVE numbers.