Friday the site read CVE-2026-123039 as a pattern piece: a root daemon on an unauthenticated local socket, the same trust-boundary failure as GPUStack's world-writable credential directory, interesting for the shape and ignorable for the vendor — community networks do not run Check Point. A re-read of the week, with everything that landed since Friday, shows that framing was incomplete, and the correction is worth its own note because of what arrived under it.
One day before the catalog entry, on November 12, Check Point's research team published "PHP2Shell Exploitation on Check Point Gateway" — an incident investigation with wave dates, source IPs, directory paths, and malware family attribution. The entry Friday's post treated as a local-only class lesson was already a fully documented, multi-stage, in-the-wild remote chain. The local socket hole is not the story of the CVE; it is the bridge in somebody else's story.
The waves¶
- Wave one, October 30: activity originating from
130.94.19[.]204hit Israeli organizations through vulnerable Mobile Access portals. Some compromises confirmed by the investigators, and the first wave turned destructive: a wiper (destroy_v6) deployed on ESXi, with politically themed drop files (DREAM_ANNEXATION.txt) naming a rival security brand. - Wave two, November 2: a broader scan and exploitation pass across multiple countries and sectors, including some of the same Israeli targets, with no destructive activity observed. No sector preference — opportunistic initial access, not a targeted campaign.
- The timing marker matters as much as the geography: exploitation began about one week after the fix for the portal vulnerabilities became available. The window that mattered was never the advisory-to-KEV gap; it was the fix-to-applied gap, the same one this site keeps measuring in every KEV batch post.
The chain, step by step¶
The steps as reconstructed in the vendor write-up:
- Initial access: PHP2Shell through Mobile Access. The portal runs on an Apache/PHP stack, and the exploited pair — CVE-2026-109618 and CVE-2026-109619 — is exactly the PHP runtime pair this site named on October 22 as
php2shell: unauthenticated RCEs reachable wherever PHP runs with vulnerable versions. The forensic residue in the investigation is a PHP session directory (/opt/CPcvpn-R81.20/tmp/) holdingupload_progress_pwnmarkers, and Apache/PHP workers segfaulting hundreds of times during the exploit attempts. - Escalation: the unauthenticated root daemon. From the portal service account, the attacker sent commands to the DynamicCLI IPC socket (
/tmp/dynamic_socket) that accepts connections from any local process and executes them with root rights. This is CVE-2026-123039 — the "Incorrect Permission Assignment" that earned the wrong-sounding product name in the catalog row, and the piece Friday's post called a world-writable root listener. Here it is in use, as the single step between a web shell and the appliance kernel. - Persistence: webshells in the template directory. Root command execution dropped base64-decoded PHP webshells into
<templates>/zz<random>.tpl— files the portal builds its login pages from. A gateway that serves a shell to whoever loads its sign-in page. - Second-stage tooling: TSGA and TSProxy. Deployed with privileged command access, and identified as modified variants of PhiliKit, the malware framework ESET documented in attacks on Ivanti appliances and associated with the China-nexus actor it tracks as UNC5221. Shared code, configuration, and crypto material.
- The pivot: gateway to ESXi over SSH. The attackers moved from the gateway to a VMware ESXi host, which is where the wiper ran and the brand-named notes appeared.
The attribution hole, kept open¶
The vendor lists the possibilities their own evidence allows: the identified actor ran the whole campaign, acted only as an initial-access broker, joined someone else's operation, or ran it as a false flag — and it is possible the destructive stage was a smoke screen. The brand-name note is circumstantial: Dream Security had just published research on PHP2Shell exploitation of Palo Alto devices, and the file dropped during the destructive wave carried Dream's name. Retaliation, taunting, and misdirection all fit that datum. The PhiliKit lineage connects the tooling to a group with prior appliance-chaining history, but connection is not attribution. This site reports the possibilities because the write-up itself does not pick one, and neither should you.
What it means for this site's PHP2Shell thread¶
The October 22 post argued that the two runtime bugs — the php-fpm pair with the unauthenticated default config — made PHP's version and configuration somebody else's problem in every deployment that embeds a language runtime. Here is that argument's cleanest datapoint yet: the two CVEs this site named in the month's most-cited runtime story were walked straight through a firewall vendor's portal code a week after their fix shipped, because portal code is code, and portal code that runs PHP inherits PHP's CVEs. Appliance vendors get no exemption from the runtime inventory homework. Neither does anyone who pinned latest-ce on a PHP image in August, as this site recorded internally with its own Passbolt pinning.
Homework¶
- Patch both layers, not one. The Mobile Access portal pair needs the runtime fix the vendor shipped; the DynamicCLI hole needs hotfix
sk1000362. Patching only the portal leaves the bridge standing in the other direction. - If the portal CVEs ran unpatched after ~October 22, assume the compromise went to root. The chain in the write-up is mechanical, not exotic; treat any unpatched Mobile Access exposure in the window as breached, per the catalog's forensic-triage requirements (BOD 26-04, deadline November 16 for federal operators — and the catalog does not know your infrastructure exists).
- Hunt the four artifacts: the
upload_progress_pwnmarker under the portal's PHP session directory, segfault storms in the Apache/PHP worker logs,zz*.tplfiles in the portal's<templates>directory, and TSGA/TSProxy process names in the running set. Any hit means the appliance is not yours — rebuild it rather than clean it. - Segment the gateway from the virtualization plane. The wiper landed on ESXi one SSH hop away from the compromised appliance. A security gateway is not a jump host; cut the SSH path from appliance to hypervisors and the chain loses its terminal step.
- Keep the portal logs long enough for forensics. The investigation's timeline is readable only because segfault storms and session artifacts survived. Short log rotation turns your incident into somebody else's.
The honest column¶
- This is vendor research on the vendor's own product, published with paths, IPs, and tooling detail sufficient to act on. That cuts both ways in the usual place: nobody knows the product's blind spots better, and nobody has an interest in the story's framing. The site treats it as the best available account with the caveat attached.
- The catalog certified exploitation on November 13, fourteen days after wave one — and after both fixes existed. The certification lag is the smallest gap in this story; the fix-to-applied gap is the one that owned the exploitation window.
- No attribution is sustained. The China-nexus association rides on tool lineage, not on the operation itself. The false-flag scenario is in the vendor's own text. Report it the way it is written down.
- The site's Friday framing — "the pattern rather than the product" — is corrected where it was wrong: the product exploitation record exists and is specific. The pattern reading stands: trustless privileged listeners erase the local boundary, and Friday's GPUStack comparison was not wasted ink. Both things were true at once.
Sources¶
Check Point Research: PHP2Shell Exploitation on Check Point Gateway, November 12, 2026. Check Point advisory sk1000362 (CVE-2026-123039, DynamicCLI). CVE-2026-123039 record (published November 12, NVD Undergoing Analysis, CVSS 3.1 7.8). CISA alert, November 13, 2026 and the KEV catalog JSON (fetched 2026-11-16T02:03-07:00 — dateAdded 2026-11-13, dueDate 2026-11-16, catalog version 2026.11.13). ESET APT Activity Report Q4 2025–Q1 2026 (PhiliKit, UNC5221). Dream Security: chained PHP2Shell exploit roots 25 servers. This site's PHP2Shell post, October 22 and Friday's KEV batch post.