On October 20, details of two critical vulnerabilities in PHP itself leaked online. PHP is the language behind roughly 70% of the world’s websites, from WordPress and Magento to government portals and online stores. The vulnerabilities, dubbed PHP2Shell (CVE-2026-109618 and CVE-2026-109619), were rated 9.2 out of 10. The worst part: they allowed an attacker to run their own code on a server without any authentication — to steal data, change website content, or leave a backdoor.
A 14-year-old bug
How the flaw was found is a story in itself. It had been hiding in PHP’s code for about 14 years, and three independent research teams — Calif, Wiz, and OpenAI — discovered it almost simultaneously, with the help of AI models. The PHP developers planned to quietly release a fix on October 22, but the details leaked on social media two days early. From that moment, it wasn’t only defenders who knew about the vulnerability, but attackers too: within days, Cloudflare recorded millions of exploitation attempts across its network.
The day the internet went into emergency mode
On October 21, the internet effectively went into a state of emergency. Government websites in the Netherlands, Finland, France, Canada, the UK, and other countries were taken offline for hours as a precaution — even the Dutch National Cyber Security Centre temporarily shut down its own site. The Internet Archive, parts of Wikipedia’s services, banks, and hospitals went dark. In Japan, airline ANA, railway operator JR West, and MUFG bank suspended some of their pages, and Prime Minister Sanae Takaichi personally called on businesses via social media to act that same evening. Cybersecurity agencies, from the US NSA to CERT-EU, repeated the same message: update immediately, or take your site offline until you can.
Why this matters especially for e-commerce
For an online store, a breach is more than just “the site is down.” It means customer databases with phone numbers and addresses, order history, and access to the admin panel and payment integrations. And taking a site offline “just in case” means hours without sales, disrupted ad campaigns, and shoppers leaving for competitors. That’s why in situations like this, the winners are those who can update quickly without stopping their business.
What we did
As soon as the PHP developers released the patches, our team started updating client servers — and by the end of the same day, most SoloMono stores were already running on secure versions. No downtime, no lost orders, and no action required from store owners.
If you run other PHP websites outside our platform, check your version: the patched releases are 8.5.12, 8.4.27, 8.3.36, and 8.2.35. Older branches (8.1 and below) are no longer officially supported, so they should be upgraded as soon as possible.
That’s exactly what a platform is for: security, updates, and infrastructure are our job, so you can focus on selling. If you have any questions about your store, contact our support team and we’ll check everything for you.