Hey folks, I'm posting this here as well since there are certainly some of you here with PHP in your process.
The entire CRM is on a High Level platform and High-level accounts are indirectly but seriously vulnerable if the service they use runs an unpatched PHP web server. The flaw is not in your password or account itself, it lets attackers compromise the server, potentially read passwords, session tokens, API keys, and certificates from server memory, then use those to access privileged accounts.
I am not being hyperbolic. This is CRITICALY serious and should be your #1 priority to ensure all is set.
If you use ANY API_KEY variables ANYwhere, go rotate them NOW. Imagine someone just got unlimited access to your personal phone serious.
I'm not allowed to offer help, but I'm sure the AI Team can cary you through it.
#onlyquittersfail.
-------------------
Two critical vulnerabilities in 𝗣𝗛𝗣 were patched on 21 October 2026.
The researchers call the attack chain 𝗽𝗵𝗽𝟮𝘀𝗵𝗲𝗹𝗹: CVE-2026-109618 and CVE-2026-109619, both rated 𝗖𝗩𝗦𝗦 𝟵.𝟮. An unauthenticated attacker can run code on your server. Exploit attempts were seen hours before the patch even shipped.
PHP serves as the foundational architecture for an estimated 𝟳𝟬% 𝘁𝗼 𝟳𝟱% 𝗼𝗳 𝗮𝗹𝗹 𝘄𝗲𝗯 𝘀𝗲𝗿𝘃𝗲𝗿𝘀 𝗴𝗹𝗼𝗯𝗮𝗹𝗹𝘆, the potential attack surface is unprecedented.
Telemetry compiled Wednesday morning by Palo Alto Networks Cortex Xpanse identified more than 𝟮𝟮.𝟲 𝗺𝗶𝗹𝗹𝗶𝗼𝗻 𝗶𝗻𝘁𝗲𝗿𝗻𝗲𝘁-𝗲𝘅𝗽𝗼𝘀𝗲𝗱 𝘀𝗲𝗿𝘃𝗲𝗿𝘀 𝗿𝘂𝗻𝗻𝗶𝗻𝗴 𝗽𝗼𝘁𝗲𝗻𝘁𝗶𝗮𝗹𝗹𝘆 𝘃𝘂𝗹𝗻𝗲𝗿𝗮𝗯𝗹𝗲 𝗣𝗛𝗣 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲
-----------------------------------
🎯 𝗪𝗵𝘆 𝘁𝗵𝗶𝘀 𝗵𝗶𝘁𝘀 𝘆𝗼𝘂 𝗲𝘃𝗲𝗻 𝗶𝗳 𝗪𝗼𝗿𝗱𝗣𝗿𝗲𝘀𝘀 𝗶𝘀 𝗳𝘂𝗹𝗹𝘆 𝘂𝗽𝗱𝗮𝘁𝗲𝗱
The bug is in 𝗣𝗛𝗣 𝗶𝘁𝘀𝗲𝗹𝗳, the programming language WordPress runs on. It is not in WordPress, not in a theme, not in a plugin.
That means: a perfectly updated WordPress site on an unpatched PHP version is 𝘀𝘁𝗶𝗹𝗹 𝘃𝘂𝗹𝗻𝗲𝗿𝗮𝗯𝗹𝗲. Core updates, plugin updates and auto-updates do nothing here. The fix lives on the server.
-----------------------------------
✅ 𝟯 𝘀𝘁𝗲𝗽𝘀, 𝟱 𝗺𝗶𝗻𝘂𝘁𝗲𝘀
1️⃣ 𝗖𝗵𝗲𝗰𝗸 𝘆𝗼𝘂𝗿 𝗣𝗛𝗣 𝘃𝗲𝗿𝘀𝗶𝗼𝗻. WP Admin > Tools > Site Health > Info > Server > "PHP version".
2️⃣ 𝗖𝗼𝗺𝗽𝗮𝗿𝗲 𝗶𝘁 𝘁𝗼 𝘁𝗵𝗲 𝗳𝗶𝘅𝗲𝗱 𝗿𝗲𝗹𝗲𝗮𝘀𝗲𝘀: 8.5.12 / 8.4.27 / 8.3.36 / 8.2.35 (or newer). If your number is lower inside the same branch, you are not patched yet.
3️⃣ 𝗔𝗰𝘁, 𝗱𝗲𝗽𝗲𝗻𝗱𝗶𝗻𝗴 𝗼𝗻 𝘄𝗵𝗲𝗿𝗲 𝘆𝗼𝘂 𝗵𝗼𝘀𝘁:
• 𝗠𝗮𝗻𝗮𝗴𝗲𝗱 𝗪𝗼𝗿𝗱𝗣𝗿𝗲𝘀𝘀 𝗵𝗼𝘀𝘁 (WP Engine, Kinsta, SiteGround, Cloudways, Raidboxes and co): most of them patched their platform on 21 October. Open a ticket anyway and ask them to confirm the exact PHP patch version running on 𝘆𝗼𝘂𝗿 site. Do not assume.
• 𝗢𝘄𝗻 𝗩𝗣𝗦 𝗼𝗿 𝘀𝗲𝗿𝘃𝗲𝗿: update today, then restart. apt update && apt upgrade or dnf update, followed by a restart of php-fpm or Apache. The restart matters: running workers keep the old, vulnerable code in memory.
• 𝗣𝗛𝗣 𝟴.𝟭, 𝟴.𝟬, 𝟳.𝟰 𝗼𝗿 𝗼𝗹𝗱𝗲𝗿: this is the painful one. Those branches get 𝗻𝗼 𝗼𝗳𝗳𝗶𝗰𝗶𝗮𝗹 𝗳𝗶𝘅. Your options are to upgrade to 8.2 or newer, install your Linux distribution's backported package if one exists, or take the site offline until you have done it. CISA explicitly recommends taking PHP 8.1-and-older systems offline until they are updated.
If you look after client sites: check every one of them, plus staging and test installs. Old forgotten installs are exactly what gets hit.
-----------------------------------
⛔ 𝗪𝗵𝗮𝘁 𝗻𝗼𝘁 𝘁𝗼 𝗱𝗼
• 𝗗𝗼 𝗻𝗼𝘁 𝗶𝗻𝘀𝘁𝗮𝗹𝗹 𝗮 "𝗽𝗵𝗽𝟮𝘀𝗵𝗲𝗹𝗹 𝗳𝗶𝘅" 𝗽𝗹𝘂𝗴𝗶𝗻. No WordPress plugin can patch the PHP interpreter. Anything claiming otherwise is useless at best and a backdoor at worst.
• 𝗗𝗼 𝗻𝗼𝘁 𝘁𝗿𝘂𝘀𝘁 𝗽𝗵𝗽.𝗶𝗻𝗶 𝘀𝗻𝗶𝗽𝗽𝗲𝘁𝘀 𝗳𝗿𝗼𝗺 𝗳𝗼𝗿𝘂𝗺𝘀. The PHP team is blunt about it: there are no complete mitigations, updating is the only safe choice.
• 𝗗𝗼 𝗻𝗼𝘁 𝘄𝗮𝗶𝘁 𝗳𝗼𝗿 𝗮𝘂𝘁𝗼-𝘂𝗽𝗱𝗮𝘁𝗲𝘀. WordPress auto-updates never touch PHP.
-----------------------------------
🔍 𝗜𝗳 𝘆𝗼𝘂𝗿 𝘀𝗶𝘁𝗲 𝗿𝗮𝗻 𝗮𝗻 𝗼𝗹𝗱 𝗣𝗛𝗣 𝘃𝗲𝗿𝘀𝗶𝗼𝗻 𝗮𝗻𝗱 𝘄𝗮𝘀 𝗿𝗲𝗮𝗰𝗵𝗮𝗯𝗹𝗲 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸
Treat it as potentially probed. Things worth a look:
• Unexplained PHP worker restarts or bursts of HTTP 500 errors
• Requests with multipart/form-data followed by memory-limit errors in the log
• Unusually large PHPSESSID cookies
• New or modified .php files in wp-content/uploads or the theme folder
If anything looks off, rotate everything the server could have held: database password, WordPress admin passwords, API keys, and the salts in wp-config.php. Rotating the salts logs every session out, which is what you want. One half of this bug leaks raw server memory back to the attacker, so any secret that passed through that server is suspect.
Sitting behind Cloudflare helps a little. They pushed WAF rules for the known attack paths, free plans included. That is a stopgap, not a fix.
-----------------------------------
📚 𝗦𝗼𝘂𝗿𝗰𝗲𝘀
𝗕𝗼𝘁𝘁𝗼𝗺 𝗹𝗶𝗻𝗲: checking takes five minutes. If you are still on PHP 8.1 or older, today is the day that upgrade finally happens.
Questions? Drop them in the comments. No DMs please.