Update 15 Nov 2026 (06:48 Asia/Gaza): PHP2Shell is now being used against Check Point firewall and VPN gateways
Check Point Research says that from 30 October 2026 an attacker used PHP2Shell (CVE-2026-109618 and CVE-2026-109619) to break into unpatched Mobile Access portals on Check Point Security Gateways. The attacker then gained root through a second, Check Point-specific flaw, CVE-2026-123039 in the Gaia OS DynamicCLI service, and installed PHP webshells and a persistent backdoor. In a limited number of cases the attacker moved from the gateway to a VMware ESXi host and ran a wiper.
According to Check Point, the first wave on 30 October targeted Israeli organisations, with destructive activity against some of them. A broader second wave on 2 November reached organisations in several countries and sectors, with no evidence of destructive activity. Activity was seen until 4 November. The Check Point advisory says a couple of dozen unpatched systems were compromised, that fixes had been available since 23 October, and that affected customers were notified. Check Point says the evidence does not let it assess with high confidence who was behind the operation, and we do not attribute it.
On 13 November CISA added CVE-2026-123039 to its Known Exploited Vulnerabilities catalogue. The KEV entry sets a due date of 16 November 2026 for US federal agencies and marks forensic triage as required. The PHP2Shell advice in the rest of this article (update PHP for websites and servers) is unchanged.
Running a Check Point gateway with Mobile Access?
- Install the fix: Check Point recommends the November Jumbo Hotfix on all Management Servers and Security Gateways, starting with internet-facing Mobile Access deployments. Per sk1000362, CVE-2026-123039 is fixed from Jumbo Hotfix Accumulator R82.20 Take 14, R82.10 Take 52, R82 Take 132 and R81.20 Take 174.
- Stopgap if you cannot patch yet: sk1000362 describes stopping the
dynamic_serverprocess and preventing it from restarting. Check Point notes this makes the Dynamic CLI commands fail until it is re-enabled. - Check the logs: sk1000362 explains how to review
/var/log/dynamicCli.logon each gateway or cluster member for commands that do not use the expected Clish wrapper. Follow the checks in the article itself; the Check Point Research post and the advisory list further indicators. - Check ESXi hosts reachable from the gateway: in the investigated intrusion the attacker reached a VMware ESXi host over SSH from the gateway. Review SSH access and logins on those hosts.
Check Point warns that finding no indicator does not rule out compromise, and a match needs immediate investigation. Affected products and versions are listed in sk1000362 and in the advisory table.
Update, 27 Oct 2026: exploitation in the wild is now confirmed. What changed since we published:
- CISA: on 26 October it added CVE-2026-109618 and CVE-2026-109619 to its Known Exploited Vulnerabilities catalogue. US federal agencies must patch by 29 October.
- Confirmed attacks: BleepingComputer reported on 26 October that Perplexity’s detection lead Adel Karimi recorded successful remote code execution on honeypots running PHP 8.4.26 under Apache
mod_php. He stresses it was a deliberately favourable single-worker set-up. Expel’s Marcus Hutchins called it the highest-quality confirmation he had seen. Researchers quoted by SC Media still see no reliable mass exploitation. - UAE exposure: Khaleej Times reports, citing Censys, that 4,691 internet-facing hosts in the UAE are potentially exposed, “representing 79.5 per cent of the country’s total versioned hosts”.
- The $2,000 challenge: the public “Steal My Bitcoin” challenge was solved on 25 October. The organiser confirmed the solve and made the transfer, admitting he had first put the wrong wallet key on the server; The Register reports the prize was about $2,000.
- Retraction: Palo Alto Networks’ Unit 42 on 25 October withdrew its earlier report linking an attack on a European government agency to these CVEs, saying it could not confirm that link.
Our advice is unchanged: update PHP now, restart the web service, then check your logs.
The short answer
The biggest PHP vulnerability 2026 has produced so far is a pair of flaws nicknamed php2shell: CVE-2026-109618 and CVE-2026-109619. On 21 October 2026 the PHP project shipped fixes in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Both flaws sit in the PHP engine itself, not in WordPress, Laravel or any plugin, and both can let an unauthenticated web request end in remote code execution on the server. PHP rates them 9.2 on CVSS v4. The update button in your WordPress dashboard does not touch the PHP engine. Your host, your server team or your Docker image has to change.
Is anyone being hacked through it yet? Yes, at least in some cases. On 26 October CISA added both CVEs to its Known Exploited Vulnerabilities catalogue, after researchers confirmed successful exploitation on honeypots (see the update above). Until then CISA had said it had not observed successful exploitation, and one vendor had to withdraw an early “successful exploitation” claim. The sensible reading now: exploitation is real, a confirmed wave of mass break-ins has not been documented, and the window to patch quietly has closed.
This guide explains what broke in plain language, what the official sources actually say, how to see which PHP version really serves your site, and a practical checklist for WordPress, WooCommerce and Laravel teams in the UAE, Saudi Arabia and Egypt. It contains no exploit steps.
What happened, with dates and sources
- 20 October 2026: the PHP project gave advance notice of a critical security release. Linux distributions and long-term-support vendors received the patches early.
- 21 October 2026: PHP published its security advisory and the fixed releases 8.5.12, 8.4.27, 8.3.36 and 8.2.35. The same day, CISA urged organisations to patch immediately, and Cloudflare deployed WAF rules for both CVEs.
- 22 October 2026: CERT/CC published vulnerability note VU#763488. Sophos reported a public proof of concept and, the same evening, corrected an earlier claim of a successful compromise.
- 23 October 2026: CISA revised its alert with a SIGMA detection rule. The FBI issued public service announcement PSA261023 telling operators to update or take affected systems offline.
- 25 October 2026: Unit 42 retracted its 23 October report linking an attack on a European government agency to the flaws. The public “Steal My Bitcoin” challenge was solved (The Register).
- 26 October 2026: BleepingComputer reported confirmed in-the-wild remote code execution on honeypots. CISA added both CVEs to its KEV catalogue the same day.
What actually broke, in plain language
PHP describes two separate bugs. CVE-2026-109618 is an out-of-memory problem: when PHP runs out of memory part-way through a request, internal request data can be left half-initialised, and the clean-up code may then treat that invalid data as valid. CVE-2026-109619 is about stale state: some request-owned internal state can survive after its memory has been freed, and a later request handled by the same worker may touch it before normal initialisation resets it.
The details matter less than three practical consequences:
- No login is needed. PHP says it has seen a demonstrated attack where an unauthenticated request triggers the bug before any application code runs.
- Your application cannot protect itself. Because the problem happens inside the engine, a security plugin, a Laravel middleware or a WordPress hardening setting runs too late.
- Every web-facing PHP set-up is in scope. CISA lists Apache with mod_php (which PHP considers the highest risk), PHP-FPM, php-cgi, FrankenPHP and LiteSpeed.
How the php2shell flaw works (the anatomy)
This section explains the mechanism so you can judge the risk for yourself. It deliberately omits a working exploit — there is no copy-paste payload here, and nothing below will run as-is. The goal is understanding, not weaponisation.
Where the bug lives. Both flaws sit deep in PHP’s request engine, not in your code. PHP uses a short-cut called longjmp() to bail out of a request the instant it runs out of memory (an “out-of-memory”, or OOM, event). The problem, in PHP’s own words, is that in certain moments request memory is reachable before it has been fully initialised. If an allocation fails at exactly that moment, PHP jumps out without accounting for the half-built state, and the request-shutdown code then reads or branches on memory that is in an invalid state. That is CVE-2026-109618. The second bug, CVE-2026-109619, is the same idea across the request boundary: some worker-wide “global” state (error, session or extension state) still points at memory owned by a previous request, and a later request touches that stale pointer before normal initialisation can reset it — a classic use-after-free.
Why it allows unauthenticated RCE. Three facts combine into the danger:
- It fires before your application runs. On Apache
mod_php, the request-shutdown procedure runs unconditionally — even when request startup already failed during PHP’s automatic parsing of the request body. So the vulnerable code path is reached before a single line of WordPress, WooCommerce or Laravel executes. No login, no valid route, no plugin bug required. - The attacker controls the trigger. PHP parses
multipart/form-databodies automatically. An attacker can shape that body to drive the worker to its memory limit at a chosen instant — PHP lists several “OOM strategies”, such as a multipart request with no usable declared length, a part carrying an unbounded number of headers (which cost far more memory inside PHP than on the wire), or empty file controls and deeply nested field names that multiply the work. - Invalid state becomes control. Once shutdown reads that invalid or freed memory, an attacker who has carefully groomed the heap can make the dangling value point at bytes they chose, turning a memory-corruption bug into remote code execution as the web-server user. PHP confirms a validated, application-independent RCE against default
mod_phpwith normal memory limits and a standard multi-worker prefork setup.
The general shape of a malicious request. An automated attacker does not send anything that looks like a hack. It sends a heavy, malformed upload to any URL that reaches PHP, engineered so the engine runs out of memory at the wrong moment. Redacted and illustrative only — placeholders and ellipses stand in for the parts that would make it function, which are omitted on purpose:
POST /<any-path-that-reaches-php> HTTP/1.1
Host: your-site.example
Transfer-Encoding: chunked ← no usable Content-Length, so the size check is skipped
Content-Type: multipart/form-data; boundary=----x
------x
Content-Disposition: form-data; name="a[...][...][...]" ← deeply nested names multiply internal work
X-Filler: .................... ← one part carrying a huge number of headers,
X-Filler: .................... repeated enough to exhaust memory_limit
... (heap-grooming and the memory-exhaustion trigger omitted for safety) ...
------x--
What lands on the server is just an oversized, malformed POST. What the attacker gains, if it works, is the ability to run commands as the web account — enough to drop a webshell, read wp-config.php or a Laravel .env for database and API credentials, and move on. CVE-2026-109619 adds a quieter variant: two ordinary-looking requests to the same worker, one planting stale state (helped on PHP 8.5 by fatal_error_backtraces, or via the session.upload_progress path) and the next consuming it.
The single most important takeaway: because all of this happens inside the engine, before your code, you cannot patch it in your application. Only upgrading PHP — or, for unsupported branches, taking the site offline — closes it.
What happens if you don’t patch
Picture a WooCommerce store in Dubai or a Laravel booking app in Cairo left on an unpatched PHP build. Here is the realistic sequence, grounded in the sourcing below:
- You are found automatically. This is not a targeted hunt. Cloudflare reported attempts jumping from thousands before disclosure to, in its founder’s words, millions afterward, and deployed managed WAF rules on 21 October. Mass internet-wide scanning for vulnerable PHP is already underway, so an unpatched site is located in hours, not weeks.
- A probe becomes a foothold. The scanner fires the malformed uploads described above at common paths. On a vulnerable
mod_phphost it can gain code execution as the web user; Sophos observed attempts delivering a Mirai-family botnet payload (it withdrew an early “successful compromise” claim the same day, so treat in-the-wild success as disputed — see below). - A webshell is dropped. The attacker writes a small script into a web-reachable folder (uploads, cache, a theme directory) to keep access even after you later patch. From there your server can be enrolled into a botnet or used to attack others.
- Data is stolen.
wp-config.phpand Laravel.envfiles hand over database credentials, payment keys and API tokens. Customer names, phone numbers, national ID numbers and order history can be exfiltrated — which in Saudi Arabia can trigger breach-notification duties under the PDPL, and reputational and contractual fallout everywhere. - Defacement or extortion. The visible end is sometimes a replaced homepage; more often it is quiet persistence, cryptomining, or a ransom note weeks later.
Keep the stakes honest: CISA said on its 23 October revision that it had not observed successful exploitation in the wild at publication, and neither CVE was in its KEV catalogue as of 23 October (CISA added both on 26 October, after confirmed exploitation). Researchers quoted by Cybersecurity Dive note many public proofs of concept are unreliable, that VulnCheck found most depend on display_errors being on, and that Mandiant validated code against default mod_php but not PHP-FPM, while warning limited exploitation may have begun. The right posture is not panic — it is patch today, because the gap between “scanning” and “confirmed mass compromise” has historically been measured in days.
Check if you’re exposed: a two-minute self-test
Run these on your own site only. None of them is an attack; they just read your configuration.
The patched line. You are exposed if your live version is below the fix for its branch:
| Your branch | Patched (safe at or above) |
|---|---|
| PHP 8.5 | 8.5.12 |
| PHP 8.4 | 8.4.27 |
| PHP 8.3 | 8.3.36 |
| PHP 8.2 | 8.2.35 |
| PHP 8.1 and older | No upstream fix — upgrade or take offline |
- Find the live PHP version. Use the method for your setup from the section above — WordPress Site Health (Tools → Site Health → Info → Server → “PHP version”), your hosting panel’s PHP selector, or
php -v/php-fpm8.3 -vinside the live worker. Write the number down. - Compare it to the patched line in the table above. If your number is below the “safe” version for its branch, you are exposed.
- Check it from the outside, safely. Running
curl -I https://your-site.example/against your own site sometimes shows anX-Powered-By: PHP/...header with the version. Many hosts hide it, and a hidden header does not mean you are safe. The live-worker number from step 1 is the source of truth. - Act on the result. If you are on or above the safe version, record the date and move on. If you are below it, upgrade to the fixed release for your branch today, restart PHP-FPM or Apache, and re-check from the live worker. If you are on PHP 8.1 or older with no vendor backport, follow CISA’s advice and take the site offline until it is upgraded. Then work through the full checklist below.
Which PHP versions are affected and which are safe
- PHP 8.5: anything before 8.5.12 is affected.
- PHP 8.4: anything before 8.4.27 is affected.
- PHP 8.3: anything before 8.3.36 is affected. (ifynx.com itself was on 8.3.33 last week and is now on 8.3.36.)
- PHP 8.2: anything before 8.2.35 is affected.
- PHP 8.1 and older: no upstream fix. CISA’s advice is blunt: if you cannot upgrade, take PHP-based systems offline until you can. Some control panels have published their own backported builds (cPanel for its ea-php74, ea-php80 and ea-php81 packages, and Plesk for its 7.4, 8.0 and 8.1 builds dated 21 October). If you rely on one of those, confirm the fix in the vendor’s changelog rather than assuming it.
The scores differ by source. PHP’s advisories give both CVEs 9.2 on CVSS v4. The US National Vulnerability Database scores CVE-2026-109618 at 9.8 and CVE-2026-109619 at 8.1 on CVSS 3.1. Either way, this is a patch-today issue.
Is php2shell being exploited? What we know and what we don’t
This is where a lot of coverage has gone too far, so here is the careful version:
- CISA (official, revised 23 October): it had not observed successful exploitation in the wild at the time of publication, but the flaws “pose a risk to organizations if left unpatched”. Neither CVE was in the KEV catalogue at its 23 October release, checked on the morning of 25 October. Update: on 26 October CISA added both to KEV, with a 29 October deadline for US federal agencies.
- FBI (official): its 23 October PSA urges immediate updates and, where that is not feasible, taking systems offline. It does not claim a confirmed wave of compromises.
- Sophos: on 22 October it first reported one successful exploitation, then corrected itself the same day: its telemetry showed scanning and a small number of failed attempts, with no evidence of a successful compromise. The attempted payload was a Mirai-family botnet variant.
- Other researchers, quoted by Cybersecurity Dive, say many public proofs of concept are unreliable, that VulnCheck found most of them depend on PHP’s
display_errorssetting being on, and that Mandiant validated some code against default mod_php but not PHP-FPM. Mandiant also warned that limited exploitation may already have begun.
Our reading for product owners: treat it as actively targeted, not yet confirmed as widely exploited, and patch as if the confirmation will arrive tomorrow. Turning display_errors off in production is good hygiene and seems to break many public scripts, but it is not a fix.
How to see which PHP version really serves your site
The number that matters is the one running inside the live web worker, not the one on your laptop or in a README.
- WordPress: go to Tools → Site Health → Info → Server and read “PHP version”.
- cPanel: open “MultiPHP Manager” or “Select PHP Version” and check the version assigned to the domain, not just the server default.
- Plesk: open the domain’s “PHP Settings”; the PHP handler and version are listed at the top.
- Docker: run
php -vinside the running web container (for exampledocker compose exec wordpress php -v). Check the container that serves traffic, not a build container. - Laravel on a VPS: check the PHP-FPM service the web server talks to (for example
php-fpm8.3 -v), not only the CLIphp -v, since they can differ.
Who applies the update
- Shared hosting (very common for SME sites in the Gulf and Egypt): open a ticket today. Quote both CVE numbers and the fixed version you need. Ask for written confirmation of the new version.
- Managed WordPress: ask which PHP builds they rolled out after 21 October and when your site moved to one.
- Docker: pin the official image to a fixed tag such as
php:8.3.36-fpmorphp:8.4.27-fpm, rebuild, recreate the containers, then runphp -vinside the new container. Restarting nginx alone does not help if PHP-FPM still runs the old binary. - VPS or dedicated server: install your distribution’s security update for PHP, restart PHP-FPM or Apache, and confirm the version from the live worker.
- Still on PHP 7.4 or 8.1: this is the moment to book the upgrade. If it cannot happen this week, take the site offline or put it behind a strict WAF rule set while you migrate, and plan the move to a supported branch.
The patch-and-verify checklist for WordPress and Laravel teams
- Inventory every PHP site you own or maintain, including staging copies, old landing pages and forgotten subdomains. PHP often hides inside other software.
- Record the live PHP version of each one using the methods above.
- Upgrade to 8.5.12, 8.4.27, 8.3.36 or 8.2.35 or later, starting with internet-facing and payment-related sites.
- Verify after the change. Reload Site Health or
php -vfrom the live worker and keep a screenshot for your records. - Turn off error display in production:
display_errors=Offanddisplay_startup_errors=Off. Log errors to a file instead. - Add hardening layers, but do not count them as the fix. PHP’s 23 October informational advisory mentions
session.upload_progress.enabled=Offas extra hardening. A WAF such as Cloudflare’s managed rules helps; CISA says a WAF “may provide some protection” only. - Check your WAF mode. Cloudflare free plans received the rules automatically; on paid plans, confirm the managed ruleset is deployed in block mode.
- Look back through logs from mid-October: unusual POST requests that end in fatal memory errors, PHP worker processes launching shells, and outbound downloads from the web server. CISA’s SIGMA rule is a good starting point.
- If anything looks wrong, treat it as an incident: rotate database and API credentials, check for new admin users and unknown files, and restore from a clean backup if needed. In Saudi Arabia, a personal-data breach can also trigger notification duties under the PDPL.
- Write it down. Note the date, the old and new versions and who confirmed them. Clients, auditors and payment partners will ask.
Why this matters for teams in the UAE, Saudi Arabia and Egypt
A large share of SME, e-commerce and agency-built sites in the region runs on WordPress, WooCommerce or Laravel, often on shared hosting or on a VPS that nobody has logged into since launch. Many of those sites also take payments, collect national ID numbers or hold customer phone numbers. That makes a pre-authentication PHP bug a business problem, not just an IT ticket. Agencies and freelancers who built sites for clients should not wait to be asked: a short message listing the version found, the version installed and the date is the most useful thing a client can receive this week.
What we changed on ifynx.com
ifynx.com runs WordPress in Docker. We pinned our PHP image to php:8.3.36-fpm-bookworm, rebuilt it, recreated the live worker and confirmed it reports PHP 8.3.36. We also set display_errors=Off and display_startup_errors=Off, so no warning can print a server path to a visitor, and added session.upload_progress.enabled=Off as an extra layer. The upgrade is the fix; the rest is hygiene.
If your team needs help auditing a fleet of WordPress or Laravel sites, iFynx builds and maintains web and app products for clients across the region. See our app development work for the UAE and Saudi Arabia, or what we do.
Frequently asked questions
Which PHP versions fix php2shell?
PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, released on 21 October 2026. Any later version on those branches is also fixed. PHP 8.1 and older have no upstream fix.
Does updating WordPress or my plugins fix the PHP vulnerability?
No. CVE-2026-109618 and CVE-2026-109619 are in the PHP engine. WordPress, plugin and theme updates do not change the PHP version; your host or server team must upgrade PHP itself.
How do I check my PHP version in WordPress?
Go to Tools, then Site Health, then the Info tab, and open the Server section. The “PHP version” line shows the version serving your site.
Is php2shell being actively exploited?
Yes, in at least some cases. CISA added both CVEs to its Known Exploited Vulnerabilities catalogue on 26 October 2026, after researchers confirmed successful exploitation on honeypots. Researchers have not yet documented reliable mass exploitation. Patch now.
Is a WAF such as Cloudflare enough?
No. Cloudflare deployed managed WAF rules on 21 October, and they help, but CISA says a WAF may provide only some protection. Upgrading PHP is the fix.
What if my site is stuck on PHP 7.4 or 8.1?
There is no upstream fix for those branches. Check whether your control panel vendor shipped a backported build and verify it in the changelog; otherwise CISA advises taking the system offline until it is upgraded.
Sources
- PHP security advisory and release announcement (php.net)
- PHP GHSA-w8hw-w9fx-j79w (CVE-2026-109618 — RCE via OOM corruption)
- PHP GHSA-6wmf-4rv5-p3rp (CVE-2026-109619 — RCE via stale global state)
- CISA alert: Critical Vulnerabilities in PHP Require Immediate Patching
- CERT/CC VU#763488
- FBI IC3 PSA261023
- Cloudflare: protections against php2shell
- Sophos: proof-of-concept exploit released, with correction
- BleepingComputer: PHP2Shell flaws now exploited in the wild (26 Oct)
- SC Media: exploitation confirmed, mass attacks remain elusive (26 Oct)
- Khaleej Times: UAE firms race to patch (25 Oct, Censys figures)
- Unit 42 threat brief, with 25 October retraction
- Challenge organiser’s solve announcement (Hacker News)
- The Register: the $2,000 PHP2Shell challenge is won (26 Oct)
- Hero photo: technician working on a server rack at the NERSC data centre, by Derrick Coetzee (via Wikimedia Commons), CC0, cropped: https://commons.wikimedia.org/wiki/File:Technician_with_laptop_working_on_server_rack_at_NERSC.jpg
Related reading
- APT Vulnerability CVE-2026-109518: Debian and Ubuntu Fixed apt Versions, How to Update apt First, and a Mirror and Proxy Checklist for Gulf and Egypt Servers
- robots.txt AI Training Opt-Out: What the New __usage_ai-training Signal Means for Gulf and Egypt Publishers, Stores and SaaS Sites, and How Not to Vanish from AI Answers
- WordPress 7.1.4 Security Release: 22 Vulnerabilities Fixed, the Upgrade-Window RCE, and the Update Checklist for Gulf and Egypt Sites
- Brotli Vulnerability CVE-2026-111497 (Node2Shell): Node.js, .NET and Python Patch Checklist for Gulf and Egypt Teams
- OpenAI Exponential Time Hypothesis Claim: Does AI Break Encryption? What Is Verified and What Gulf and Egypt Teams Should Do
- Editors Should Ship Arabic and English Without Booking an Engineer
- Shipping Reliable Platforms with WordPress, React, and Cloud APIs
- Plugin4Shell: Why SHA-Pinning Failed AI Coding Agents
- Choosing a Tech Stack for Startups: A Constraint-First Decision Framework
- Saudi PDPL Compliance in 2026: A Product Checklist
- All featured iFynx articles
