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".