$ patchitfast firstaid --steps=6
Your shop is vulnerable. Do this now.
Six steps, in the order that matters: from recognising exposure to preventing it happening again. Five minutes to read, no panic needed — and free, even if you never become a customer.
Scan my shop for freeIn short
1. Recognise your exposure
Before you change anything: know what you’re looking for. These signals tend to show up alongside a critical CVE.
- Unexplained CPU or server load, especially outside peak hours
- New or modified files and cron jobs you don’t recognise
- Unknown admin accounts or API keys
- Outbound traffic to unfamiliar IP addresses
- You’re running a PHP, Magento, Shopware or WooCommerce version listed in an active KEV advisory
2. Go safely offline — with a 503, not a 404
Do you really need to go offline while you investigate or patch? Use an HTTP 503 with a Retry‑After header, not a 404, 500 or broken page. That keeps Google reading your pages as temporary and your rankings intact. This can be done at infra level (web server, CDN or DNS), even if your PHP layer itself is the problem.
3. Isolate: limit the damage while you figure out what’s going on
Rotate passwords and API keys for admin accounts and payment integrations. Disable non-critical extensions or plugins. Take a snapshot or backup of the current state before you change anything — that’s your evidence for investigation and for your CRA file. Limit access to whoever actually needs it right now.
4. Patch — or get it patched
You don’t have to wait for a full core upgrade. The gap can often be closed at infra level — via php.ini, an FPM pool configuration, or a WAF rule — before the core patch lands. Don’t have the time, team or confidence for that? That’s exactly what patchitfast exists for.
- 01scanned
- 02shielded at infra level
- +patched
5. Verify: did the fix reach the running process too?
A rebuilt image or a "patch applied" message isn’t enough. Did the fix reach the PHP process actually handling requests now, and the container serving the next one? Test with a targeted request or scan that attempts the vulnerable call itself — not just the version string.
6. Prevent this happening again next month
The next critical CVE isn’t a year away — it’s weeks away. Continuous monitoring with instant alerts, plus a CRA audit log as proof of patching-without-delay, is the difference between sleeping soundly and the phone ringing off the hook again.
Your risk? We take it off your hands.
We’re asking you to trust something new. So we put the risk on us, not on you.
Try Monitor for two weeks. Not convinced? You get your money back, no hassle and no explanation needed.
Your first critical patch within the agreed SLA (plan under 1 hour, rollout under 4 hours) — or that month is free. And every patch has a rollback, so going back is always an option.
Frequently asked questions about this guide
Is this guide enough, or do I need patchitfast?
These are the steps you can take yourself, without us. Missing the time, the knowledge, or the certainty that the fix reaches the running process? That’s what patchitfast handles within hours, with an audit log for your CRA file.
What if I’m not sure my shop is already patched?
Our free scan checks within minutes whether the vulnerable call is still reachable — not just whether an official patch shows as "applied". That’s how you know step 5, verifying, is genuinely done.
Put your shop on the waitlist for a free scan
Not sure yet if you’re exposed? Leave your email address and domain — you’ll receive the scan report as soon as it’s ready.