14 years in the core
The vulnerable code path predates your application: any multipart POST to any PHP script reaches it — no upload form, no plugin, no app bug required.
Pre-auth RCE in PHP core, present since 2012, actively exploited — and PHP 8.1 and older will never get an official fix. We harden what you run today, verify it with a non-destructive oracle we built during our field research, and hand you proof.
Two benign requests, non-destructive by design — the same safe oracle from our research. Only check sites you own or are authorized to test.
The vulnerable code path predates your application: any multipart POST to any PHP script reaches it — no upload form, no plugin, no app bug required.
PHP 8.1 and older get no official patch. If your app can’t survive an upgrade, your choices are mitigation done properly — or hoping the exploit ecosystem stalls. It isn’t stalling.
In-the-wild exploitation began hours before the patch shipped. The simple chains work today; the harder chains are engineering problems someone is solving right now.
We identify the exact PHP version, SAPI (mod_php vs FPM), and server topology for every site — the things that decide which attack chains are even possible against you.
Our non-destructive patch oracle — one ~300-byte request, no worker crashes — establishes whether your build is exposed. Safe to run on live production.
We apply the mitigation set that fits your stack: upload-progress and session hardening, memory-limit and multipart controls at the web server, WAF rule packs (ModSecurity/nginx), and vetted community backports where they audit clean. Scheduled in a maintenance window, with full rollback.
The same oracle re-runs after hardening. You get before/after proof — not a promise — that the exploitable condition is gone.
A signed per-site report: what was exposed, what we changed, what to watch in logs (the exact exploitation shapes and IOCs from our field research).
Every engagement includes a rollback plan and a signed report. Bangladesh: bKash or bank transfer. International: card or wire.
There is no official fix for PHP ≤ 8.1 — there never will be. What we do is close the exploitable conditions around it: the upload-progress/session attack path, memory-exhaustion triggers, multipart parsing exposure, and edge filtering for the known exploitation shapes. Where a community backport exists and audits clean, we apply it. You get measured before/after proof from our oracle.
The changes are configuration- and edge-level, not application-code changes. We schedule inside a maintenance window, snapshot current config, and roll back instantly if anything misbehaves. Non-destructive is the default, always.
You can — and our public research says exactly that. But it's partial: it closes one path and doesn't touch the OOM-corruption chain, the multipart WAF bypasses, or the edge shapes we see in live attack traffic. You're paying for the complete, verified set — and for proof it worked.
Fixed price, invoiced before work starts. Bangladesh: bKash / bank transfer. International: card or wire. Hosting providers can start with one server and expand.
Exploitation of this bug family is active in the wild — we treat these as emergency engagements. Single sites typically complete within one business day of access; full servers within 48 hours including the maintenance window.
For single sites on shared hosting, control-panel access is often enough for the configuration layer; server-wide hardening needs root or your provider's cooperation. We confirm the exact access needed during scoping — no surprises mid-job.
Book a 30-minute scoping call. If a scanner is enough for you, we'll say so.