
Two critical PHP flaws are being actively exploited. Singapore's CSA and Indonesia's BSSN have both told organisations to act. For ASEAN merchants, the hard part is not the patch. It is working out whose job the patch is.
On 21 October 2026, the PHP project released emergency fixes for two critical flaws, now nicknamed PHP2Shell (CVE-2026-109618 and CVE-2026-109619).
Each flaw is rated 9.2 out of 10, about as high as these things go without the internet catching fire.
PHP runs roughly 70% of websites, so the exposure is not narrow.
Either flaw lets an unauthenticated attacker run arbitrary code on a web server. No login required. No special access. Just a vulnerable PHP installation and an internet connection.
Amazon reported an exploit attempt against its honeypot, four days before fixes shipped.
PHP released emergency fixes for both flaws.
"We are seeing early attacks emerging." (Cloudflare)
The flaws were discovered with AI assistance: researchers at Calif used OpenAI's GPT-5.6 Sol, and Wiz independently reported both.
Every major authority in the region has issued guidance. Here is what each one said — in plain terms.
Patch immediately. Where an immediate update is not feasible, take the system offline "until it can be fully mitigated."
Alert AL-2026-151: "Patch immediately." All PHP versions are affected. Check web servers for PHP even if the main site does not use it — including third-party applications and components.
Advisory issued 22 October urging website operators to patch and isolate exposed systems until secured, per the Jakarta Post.
"We are seeing early attacks emerging." WAF rules are a stopgap, not a substitute for patching. Do not stop at WAF and call it done.
Most ASEAN merchants inherited PHP inside WooCommerce, Magento, OpenCart, Laravel or a custom checkout built by an agency. The flaw is not in a plugin — it is in PHP itself. Researchers have confirmed active attacks against specific versions of WordPress, Drupal, Joomla and Magento.
That makes the question of who patches it genuinely complicated. Your tech stack touches at least four parties, and in most businesses, none of them holds the full checklist.
Assume the agency handles it. Often the assumption is not written down anywhere.
May have moved on to newer projects. Retainer scope may not include security patching. Worth asking explicitly.
Manages the server infrastructure, not the application layer. PHP version updates are usually the application owner's responsibility.
Plugin fixes only help if installed. And they fix the plugin, not the underlying PHP engine the whole shop sits on.
The action you need to take depends almost entirely on which PHP version your shop runs. Some are a straightforward update. Others require a developer or a hard conversation about legacy infrastructure.
Not sure which version you are on? That is the first question to send your agency or host this week.
This is not a theoretical concern. An attacker with server-level access through PHP2Shell can do real, measurable damage to a trading business. Three areas deserve specific attention.
Order records, contact details and admin sessions are all accessible to an attacker with server control. A breach involving personal data may trigger notification duties under PDPA (Singapore and Malaysia) or the PDP Law (Indonesia). Deadlines and thresholds differ by country and by incident. Take legal advice for your situation.
If your checkout collects card details, an attacker can inject a malicious script into that page. For PCI DSS v4.0.1, merchants under SAQ A must confirm their site is not susceptible to script attacks; other merchants must manage and detect changes to payment-page scripts (requirements 6.4.3 and 11.6.1). Hosted or redirected payment pages reduce risk but do not eliminate it. Confirm your scope with your acquirer or a PCI assessor.
Taking a shop offline to deal with a breach stops sales. A week of downtime, combined with chargebacks and lost repeat customers, can cost significantly more than the assessment you were putting off. The business case for acting now is not complicated.
You do not need to be technical to run this conversation. You need to be the person who asks. Send these to your agency, your host, and anyone else who touches your PHP stack. Good suppliers answer within a day. Silence is a finding.
This is non-negotiable to know. If they cannot answer it promptly, that itself tells you something.
There should be a named person, not a shared inbox or a vague "the team".
You want a number of days, not "regularly" or "as needed". Those words mean nothing in an incident.
Amazon reported exploit attempts from 17 October. That is the date to work from when reviewing logs.
This is a commercial and contractual question, not a technical one. The answer shapes how seriously everyone else takes the first four questions.
"Good suppliers answer within a day. Silence is a finding."
The risk from PHP2Shell is global and does not wait for a local advisory. That said, the support structures and relationships differ across the three markets.
CSA has issued public alert AL-2026-151, so documenting how you responded is sensible governance. CSA also supports SMEs through Cyber Essentials and Cyber Trust certification marks, and co-funds up to 70% of consultancy fees for eligible SMEs through CSA-appointed providers. Check current eligibility and terms at csa.gov.sg.
Exploitation is global, so the risk applies regardless of local advisories. Check your national CERT's guidance. Weigh a short, focused assessment against the alternative: a week of checkout downtime, chargebacks and the repeat customers who quietly never return.
BSSN has reportedly told operators to patch and isolate exposed systems. Agency and reseller relationships often run IT for Indonesian merchants, which makes the supplier conversation your single most important control right now.
If you sell exclusively through a marketplace (Shopee, Lazada or Tokopedia), patching the storefront is the marketplace's job, not yours. They run the infrastructure; they own the PHP.
If you also run your own website (a brand site, a direct checkout, a wholesale portal, anything served from your own server or hosting account), that site is yours. The marketplace arrangement does not cover it.
Many mid-market merchants operate both: a marketplace presence for volume and a direct site for margin and customer relationships. If that describes you, the checklist below applies to the direct site.
Five steps. One owner per step. This does not require a project plan — it requires someone deciding to do it.
You can outsource the work. You cannot outsource the accountability.
"You can outsource the work. You cannot outsource the accountability."
Ewashi's E-Commerce Exposure Check maps your PHP estate, patch ownership and checkout scripts in two to three weeks, and gives you a supplier scorecard you can use immediately — in your next retainer review, your next contract renewal, or your next conversation with your agency.
No jargon. No lengthy report that sits in a folder. A clear picture of where you stand and who is responsible for what.
This article is general information, not legal or compliance advice. Breach-notification rules and PCI obligations differ by country, by incident and by how your checkout is set up. Speak to your legal adviser, acquirer or a PCI assessor for your situation.
Sources: NSA advisory (nsa.gov) · CSA alert AL-2026-151 (csa.gov.sg) · Malay Mail · Jakarta Post · Cyberpress (Cloudflare statement) · The Register (Amazon) · Tenable FAQ · OpenAI disclosure
Ewashi | Cybersecurity consulting and training for ASEAN SMEs