Binance’s CZ Warns Users as Critical PHP Flaws Put Millions of Websites at Risk
Changpeng Zhao, co-founder and former chief executive of the cryptocurrency exchange Binance, has urged internet users to take extra care when visiting websites this week. His warning follows the disclosure of two critical vulnerabilities in PHP, a programming language that runs a large share of the internet, which can let attackers take control of unpatched web servers without logging in.
In a post on X on October 21, Zhao, widely known as CZ, told users to “be extra careful visiting ANY web site in the next few days,” adding that some website administrators do not always install security patches promptly. He named the two flaws as CVE-2026-109618 and CVE-2026-109619 and said they affect servers running popular platforms such as WordPress and Magento.
Widespread PHP patching will dictate how long crypto users remain vulnerable to credential theft and malware.
Unpatched WordPress and Magento sites may become phishing hubs, prompting heightened monitoring by exchanges and regulators.
Future attacks could target emerging blockchain services, forcing stricter server‑side security standards across the industry.
Zhao also stated that exploitation had already been confirmed in the wild and that compromised websites could be used to steal login credentials or attack visitors’ devices. He closed the post with “Stay SAFU,” a phrase drawn from Binance’s Secure Asset Fund for Users (SAFU) that the crypto community uses to mean “stay safe.”
What Are the PHP Vulnerabilities?
PHP, short for PHP: Hypertext Preprocessor, is a server-side scripting language. It runs on the web server, not in the visitor’s browser, and generates the pages users see. According to web technology survey firm W3Techs, PHP is used by roughly 70% of all websites whose server-side language can be identified.
Each flaw is tracked under the Common Vulnerabilities and Exposures (CVE) system, a public catalogue that assigns a unique identifier to every disclosed security bug. Some security reporting has grouped the pair under the name “PHP2Shell,” a reference to their ability to give attackers shell, or command-level, access to a server.
The problems sit in PHP’s core code, not in any single website or application. Both flaws carry a score of 9.2 out of 10 under version 4.0 of the Common Vulnerability Scoring System (CVSS), the industry standard for rating how severe a security bug is. A score above 9.0 falls in the “critical” category.
Both flaws allow unauthenticated remote code execution (RCE). In simple terms, an attacker can send a specially crafted web request to a vulnerable server and force it to run the attacker’s own code, without needing a username or password.
The two bugs work in different ways:
- CVE-2026-109618 involves memory corruption during out-of-memory handling. If a request reaches PHP’s memory limit at a precise moment, internal data can be left half-initialized and later treated as valid by the server.
- CVE-2026-109619 involves stale global state. Internal data from one request can remain referenced after its memory has been freed, allowing a later request handled by the same server process to reuse that freed memory.
Which Servers Are Affected?
The PHP Foundation, the nonprofit organization that funds and coordinates core PHP development, said the flaws affect every PHP installation that serves web requests. This includes common setups such as PHP-FPM (FastCGI Process Manager), Apache with mod_php, php-cgi (Common Gateway Interface), FrankenPHP, and LiteSpeed.
According to the foundation, the highest risk exists on Apache web servers running mod_php, where an unauthenticated request can trigger the flaw before any application code runs. In that configuration, security controls built into a website itself offer no protection.
Patches are available in PHP versions 8.5.12, 8.4.27, 8.3.36, and 8.2.35. Servers running older, unsupported PHP versions need a full upgrade or a backported fix from their software vendor.
Timeline of the Disclosure
The PHP Foundation detailed the release and disclosure process in a blog post on October 21. Details of the vulnerabilities began circulating on October 20, which led the PHP project to bring its scheduled security release forward by one day. The patches were published on October 21. Active exploitation attempts have since been reported, and some government websites in Europe were reportedly taken offline as a precaution while updates were applied.
Because the bugs exist in PHP itself, any application built on an unpatched version is exposed. That includes content management systems (CMS) such as WordPress, e-commerce platforms such as Magento, now sold as Adobe Commerce, and custom-built web applications.
Why It Matters for Crypto Users
Crypto users regularly visit project websites, exchange interfaces, wallet dashboards, news portals, and third-party analytics tools. Many of these services still rely on PHP-based infrastructure. A hijacked website can be turned into a phishing tool. Attackers can alter a trusted page to show fake wallet connection prompts, inject malicious scripts that capture login details, or redirect visitors to lookalike sites built to drain funds.
Some major crypto firms have said they are not exposed. Coinbase Chief Security Officer Jeff Lunglhofer said the company completed a full sweep of its environment and found no exposed PHP instances. Digital asset custodian BitGo also said its platform is not affected. These statements cover only those platforms and do not reduce risk from the wider pool of unpatched websites.
In a follow-up statement on October 22, Binance confirmed that its security teams had already implemented proactive safeguards ahead of the official PHP patch release and completed the necessary remediation on its own systems. The exchange said it continues to monitor developments and strengthen its security measures to help keep its ecosystem secure.
Zhao’s warning is the latest in a series of public security alerts from him this month. Earlier in October, he cautioned hardware wallet owners after reports of tampered Ledger devices, following an incident in which $93 million was stolen through compromised wallets.
What Users and Website Operators Should Do
Ordinary users do not need to install anything on their own devices, as the fix sits on the server side. Responsibility lies with website operators and hosting providers.
Until patching is widespread, users can lower their risk by:
- Avoiding unfamiliar websites, especially for financial or crypto activity
- Not entering passwords or connecting wallets on pages that look or behave unusually
- Opening sensitive services through saved bookmarks instead of search engine results
Website operators running PHP should update to the patched versions immediately. Where an update is not yet possible, they should apply the temporary mitigations listed in the official advisories. The period of highest risk is the window before most servers are patched, and unpatched sites will remain a threat to visitors for as long as they stay online.
Also Read: SBI Data Breach: 3,897 Customer Records on the Dark Web. Can Blockchain Protect India’s Banks?
Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions.


