In late October, two critical flaws in PHP sent site owners around the world scrambling.
Governments took vulnerable sites offline, while security teams at Amazon detected exploit attempts days before public fixes were fully deployed.
If you run a Magento store, this one crash landed on your desk.
This was a big deal because Magento–once the undisputed king of eCommerce–runs on PHP.
Consequently, every store owner had to drop what they were doing to manually audit servers, apply fixes, and assess the integrity of their site.
Shopify merchants had no such job on their to-do list.
Having worked with Magento for over a decade, we’ve watched this shift firsthand. Today, the majority of our work with Magento involves migrating brands to Shopify.
We’re not saying one security scare means every Magento store should re-platform, but it does clearly show what you sign up for when you commit to a platform that–let’s face it–is knocking on a bit.
Rewind, what happened with PHP/PHP2Shell?
PHP2Shell is the nickname for two serious bugs in PHP, the software that runs on the server and builds your store’s pages.
Every time a customer opens a product page or adds something to their basket, PHP is doing the work behind the scenes.
Think of your store as a shop inside a shopping centre. Most security problems are like a faulty lock on one shop’s door–you fix your own lock.
This was a fault in the building itself. You could have the best locks in the centre and still be exposed, because the problem sat underneath everything you control.
The bugs are in how PHP handles fatal errors, such as running out of memory.
An attacker could send a specially crafted web request that made PHP trip over itself, then use the confusion to run their own code on your server.
The flaws had sat unnoticed in PHP for more than a decade.
What makes this saga even more interesting is that two security companies, Calif.io and Wiz.io, found them independently using AI and reported them in August.
Details leaked online on 20 October, and PHP rushed out the fix the next day.
Why PHP2Shell was so dangerous
PHP2Shell scored 9.2 out of 10 on the industry’s severity scale, and four things made it especially nasty for online stores.
• No login needed. An attacker didn’t need a password, a staff account or a customer account. A web request was enough.
• It struck before your store’s code ran. Tidy code, up-to-date extensions and store-level security tools made no difference, because the attack happens inside PHP first.
• The payoff is your whole business. Someone running code on your server could add a card skimmer to your checkout, copy passwords and API keys from memory, or take the site offline.
• The reach was huge. PHP runs about 70% of websites whose server language is known, and the flaws affected every version back to PHP 5.4.
The attackers didn’t wait for the announcement either.
Amazon saw the first attempt on 17 October, four days before the fix existed. Cloudflare’s CEO reported millions of attempts once the news broke, and in the UK the British Independent Retailers Association told retailers to contact their developers or hosts as a priority.
It’s worth being straight about the limits of what’s known.
Not every PHP site was equally exposed, and many attempts failed. Security firm Sansec says public exploits need specific conditions on the target server. Some early reports of successful attacks were withdrawn, and the number of real breaches isn’t known.
But the US cyber security agency CISA does class both flaws as actively exploited. And an exposed store owner can’t assume they were one of the lucky ones.
Someone has to manually check, which is why this was such a huge deal.
How does PHP2Shell affect Magento stores? Why was Magento the main target?
Magento is written in PHP and can’t run without it, so a flaw in PHP is a flaw underneath every Magento store.
Researchers confirmed the attack against Magento 2.4.9, the latest release, so being fully up to date on Magento did nothing to fix the vulnerability.
The fix is a PHP update on the server, followed by a restart of every PHP process.
If you haven’t already, check for signs of a break-in and change any passwords and keys that may have leaked.
This could be the responsibility of your tech team, your host, your agency or Adobe.
In a crisis like this, “I thought they were handling it” is a dangerous answer, so get it in writing going forward.
Older stores have it worse.
Magento 2.4.4 and 2.4.5 only support PHP 8.1, which no longer gets regular security updates from the PHP project. Those stores had to find a specially patched version of PHP from their hosting or software vendor, and they still need an upgrade.
Bad news: this wasn’t a one-off
PHP2Shell was the third critical security problem Magento store owners faced in seven weeks, and each needed a different fix.
| Date (2026) | Flaw | Severity | The Fix |
| 21 October | PHP2Shell | 9.2 out of 10 | Update PHP on every server, then restart it |
| 13 October | BlockStrap | 10 out of 10 | Apply Adobe’s October security update |
| 7 September | StyleSmuggler | 10 out of 10 | Apply Adobe’s emergency fix, after attacks began on 4 September |
These fixes don’t cover for each other. A store with the October Magento update and old PHP is still exposed, as is a store with new PHP and no Magento update.
There’s also a deadline coming. PHP 8.2 stops getting security fixes on 31 December 2026, and Adobe warns that PCI compliance is at risk from then for Magento 2.4.6 stores using it.
Adobe also makes clear that PCI compliance is the merchant’s responsibility to assess.
If you run Magento, the reality is now a pattern of frequent, unpredictable, and urgent updates to mitigate severe exploit risks.
Arriving roughly five weeks before Black Friday, the timing couldn’t have been much worse.
Does PHP2Shell affect Shopify stores? Why doesn’t Shopify have the same problem?
Shopify merchants had nothing to patch on their store, because Shopify’s core platform runs on Ruby on Rails rather than PHP. Shopify also runs its own servers, so platform security is their job rather than yours.
The bigger point goes beyond this one bug.
On Shopify, you don’t own a server, so you don’t get the 2am phone call about one. When the next serious flaw appears in the software underneath the platform, Shopify’s own teams deal with it, and no one asks you which version you’re on.
Granted, Shopify doesn’t make security someone else’s problem altogether.
Installed apps run on their developers’ own servers, and some of those run on PHP. A WordPress blog or custom tool you host separately still needs looking after too.
You’d still want to choose apps carefully, limit staff access, and turn on two-step verification.
That said, there’s a big difference between checking a handful of suppliers and being responsible for the whole stack under your store.
Where Shopify really trumps Magento
Security aside, the day-to-day case for Shopify is that you spend your money on selling rather than on keeping the platform working.
| Area | Magento (self-hosted or Adobe’s cloud) | Shopify |
| Hosting | Arranged and managed separately, or part of your Adobe setup | Hosting, SSL and unlimited bandwidth included in every plan |
| Upgrades | Manual projects that need planning, testing and budget each time | New features arrive without an upgrade project |
| Security patches | Monthly security fixes since January 2026, applied in order, plus emergency fixes | Handled by Shopify |
| Card security (PCI) | Your responsibility to assess | Shopify is certified Level 1 PCI DSS compliant |
| Running cost | Hosting, licences, extensions and developer time add up | 29% better total cost of ownership, on Shopify’s figures |
| Site speed | 53% of Adobe stores rated fast | 93% of Shopify stores rated fast |
| Checkout | Built and maintained as part of your store | Fast, hosted checkout that converts up to 5% better than Magento, on Shopify’s figures |
| Extra features | PHP extensions that need testing with each upgrade | 21,000+ apps, installed from the admin |
| Everyday marketing | Often needs a developer | Discount codes, gift cards, abandoned checkout recovery and no-code automation built in |
A word on those numbers: the cost, speed and checkout figures come from Shopify or research it commissioned, so treat them as a guide.
Your own costs are what matter, and they’re straightforward to work out.
Add up a year of hosting, licences, extension renewals, security work, upgrades and developer time. Then compare it with the Shopify plan that fits your store. Include Shopify’s transaction fees if you use a third-party payment provider.
There’s one more cost that’s harder to put on a spreadsheet. Every week your developers spend on patches is a week they aren’t improving your store.
Is Magento ever still the right choice?
Sometimes, and we’ll say so.
Very complex B2B pricing, unusually large catalogues or a real need to own every line of code can all justify staying.
Adobe also offers a Cloud Service that takes patching off your hands, though getting there is a migration project of its own.
Most of the Magento stores we see don’t need that level of complexity. They’re paying for flexibility they rarely use.
Why you should talk to Zeal
We are not a Shopify agency critiquing Magento from the outside.
We’ve spent over 10 years building, maintaining, and scaling Magento stores, and migrated numerous eCommerce brands from Magento to Shopify.
That matters because a good migration depends on understanding what you’re moving away from. Most mature Magento stores carry years of custom modules, extensions and workarounds, and not all of it should make the journey.
A proper move means working through:
• Your data: products, customers and order history.
• Your search rankings: URL mapping and redirects, so you hold on to the traffic you’ve earned.
• Your custom features: deciding what to replace with an app, what to rebuild and what to retire.
• Your integrations: ERP, stock, shipping and payments.
• Your timing: a launch that stays clear of your peak trading period.
A migration is a substantial project with a real cost, and we’ll tell you that up front.
The difference is that it’s a one-off. Magento’s upgrades, patches and emergencies keep coming back.
What to do now
If you’re on Magento, deal with the security first and the platform decision second. Don’t leave a store exposed while you weigh up a migration.
1. Get written confirmation that PHP2Shell is fixed. Ask whoever runs your servers for the PHP version and build date on each one. You’re looking for 8.5.12, 8.4.27, 8.3.36 or 8.2.35 or later, or a vendor-patched build if you’re on something older.
2. Check that the September and October Magento fixes are in place. You need both, and they’re separate from the PHP update.
3. Ask whether anyone has checked for a break-in. Patching closes the door, but it won’t remove anyone who’s already inside.
4. Check your PHP deadline. If you’re on PHP 8.2, security fixes end on 31 December 2026.
5. Work out what Magento really costs you. Include a year of hosting, licences, extensions, upgrades, developer time and emergency call-outs.
Magento or Shopify? that is the question
If you were choosing an eCommerce platform today, would you choose Magento? If your answer is “no”, “maybe”, or “not sure”, it’s worth a conversation.
Just email info@wehavezeal.com with your Magento version and a brief outline of your setup, and we’ll give you a clear idea whether migrating to Shopify makes commercial sense, and what the roadmap would look like.