ACTIVE EXPLOITATIONPHP2Shell pre-auth RCE in PHP core — emergency patching from $10/site, EOL PHP coveredPHP2Shell RCE — patch from $10→
Emergency service · CVE-2026-109618 / CVE-2026-109619

PHP2Shell patching for servers
that can’t upgrade.

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.

Check your site

Is your server exposed?

Free exposure check

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 situation

Why waiting isn’t a plan.

01 / 03Since 2012

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.

02 / 03No official fix

EOL means exposed forever

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.

03 / 03In the wild

Attacks are already firing

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.

What we do

Five steps, fixed scope, measured outcome.

  1. Step 01

    Fingerprint

    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.

  2. Step 02

    Baseline check

    Our non-destructive patch oracle — one ~300-byte request, no worker crashes — establishes whether your build is exposed. Safe to run on live production.

  3. Step 03

    Harden

    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.

  4. Step 04

    Verify

    The same oracle re-runs after hardening. You get before/after proof — not a promise — that the exploitable condition is gone.

  5. Step 05

    Report & watch

    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).

Fixed pricing

No quotes, no hourly meter — the price is the price.

Single website

Site owner

$10 per site · one-off
  • Full fingerprint + exposure check
  • Config hardening for your PHP version — including EOL 5.6 / 7.x / 8.0 / 8.1
  • WAF / web-server rules where you control the server
  • Before/after oracle verification
  • Signed mitigation report
Start now
Hosting providers & resellers

Per server

$100 per server · up to 100 sites included
  • Every site on the server covered
  • Server-wide hardening (cPanel/WHM, Plesk, bare nginx/Apache)
  • Edge + ModSecurity rule deployment
  • Per-site verification across the whole estate
  • Rollback plan + maintenance-window scheduling
  • Provider summary report for your own customers
Start now
Large estates

Beyond 100 sites

+$0.50 per extra site, same server
  • Same full coverage — no tiering of protection
  • Volume continues at $0.50/site on that server
  • Multi-server estates: quoted as one engagement
  • Priority scheduling during active exploitation windows
Start now

Every engagement includes a rollback plan and a signed report. Bangladesh: bKash or bank transfer. International: card or wire.

Questions

Straight answers.

My PHP is 7.4 / 5.6 — end-of-life. Can you actually fix it? +

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.

Will this break my site? +

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.

Can't I just set session.upload_progress.enabled=0 myself? +

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.

How do I pay? +

Fixed price, invoiced before work starts. Bangladesh: bKash / bank transfer. International: card or wire. Hosting providers can start with one server and expand.

How fast can you start? +

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.

Do you need root access? +

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.

Start here

One finding pays for the engagement.

Book a 30-minute scoping call. If a scanner is enough for you, we'll say so.

Free website check