Start with one Emergency patch check

One WordPress or PHP site, looked at once: PHP patched to a fixed release or your host asked in writing, the fix confirmed from a live page, and a short written note of what we found.

Patch check

$395, one time, one site

We look at the PHP that's live. Where we have access, we patch it to a fixed release, restart PHP and confirm the fix from a live page. Where only your host can change PHP, we ask them in writing. Either way you get a short note of what we found and what we couldn't see. Nothing on your site changes until you've said yes.

Checked within 2 business days of getting access.
Nothing starts before you pay.
No passwords by email.

What happens, in order.

  1. You book the check

    Pay with the button above, then send us the site address and who hosts it.

  2. We ask about the site

    Who hosts it, what it is built with, the PHP version if you know it, and how it is backed up. On PHP 7.3 or older there is no official fix to apply, and we tell you before any work starts.

  3. You give us access

    Through your own invites, so you can remove it any time. The 2-business-day clock starts here.

  4. We look

    The PHP version and build your site actually runs, WordPress and plugin files compared with the official copies, the updates waiting, and the newest backup.

  5. We look through the logs we can reach

    For the known warning signs. If we see signs someone got in, we stop, change nothing, and tell you what we saw.

  6. With your yes, we patch

    A fresh backup first, then PHP updated to a fixed release, restarted, and confirmed from a live page. Where only your host can change PHP, we ask them in writing.

  7. Read the note

    What we found, what we changed and what we couldn't see. If you want it handled from then on, Watch or Patch picks up each month.

What the check includes.

PHP
Patched to a fixed release, or your host asked in writing and their answer passed on to you.
Restart and confirm
PHP restarted, and the fix confirmed from a live page, not the control panel.
Updates waiting
WordPress, plugin and theme updates listed.
Logs
One look through the logs we can reach for known warning signs.
The note
A short written note: what we found, what we changed, what we couldn't see.
When
Done within 2 business days of getting access.

What it does not include.

  • Promises that a site can't be broken into. No one can honestly make one.
  • Fixes on your host's side that we can't reach. If only your host can change PHP, we ask them in writing and pass on their answer.
  • Malware removal beyond the first look for warning signs. If we find something, we stop, tell you, and quote the cleanup.
  • Sites on PHP 7.3 or older. There is no official fix to install, so the check has nothing to apply.
  • Cleanup, forensics, breach notices or legal advice.
  • Putting Cloudflare in front of your site. We can offer it, in writing, as separate work.

Anything past the check is quoted in writing first.

When your host controls PHP

On a lot of shared and managed hosting, only the host can update PHP. Then we check everything we can from outside and inside WordPress, ask your host in writing which PHP build is live, and put their answer, with the date, in your report. We never say a site is patched until the host confirms it in writing or we see it on a live page.

The usual questions.

Can you promise my site won't be hacked?
No, and be careful with anyone who does. What we promise is the work: updates on a schedule, backups we've actually restored, a person reading alerts, and a written report of what we checked and what we couldn't see.
My host says PHP is patched. Is that enough?
Often it is. We still check it from a live page, and ask the host in writing which build is running. On PHP 8.1, 8.0 or 7.4 the version number doesn't change after the patch, so we check the build date: Oct 21, 2026 or later.
What warning signs do you look for?
For php2shell, the public ones researchers have shared: a scanner user agent named php2shell-scan, upload requests carrying PHP's upload-progress field, bursts of memory errors, PHP starting programs like wget or curl, a file at /tmp/nfs, new PHP files in the uploads folder, and admin users nobody recognizes. A sign isn't proof. We check before we tell you anything is wrong.
What happens if you find a real problem?
We stop and tell you what we found, in plain words, and what we suggest. Cleanup and anything else outside your plan is quoted before we start.
What's the difference between this and a security plugin?
A plugin runs inside WordPress. The October PHP flaws sit underneath WordPress, in PHP itself, so a plugin's firewall may not stop them. Wordfence's help pages describe its firewall as running inside WordPress. We work on the PHP, the updates, the backups and the logs.
Do I need this if my site is on a JKCA care plan?
Most care plan sites don't. Our care plans host static sites with no PHP, no login page and no database, so php2shell doesn't reach them. We'll confirm it for your site and tell you. Store sites on WooCommerce are different; ask us.
Do you only work with Seal Beach businesses?
No. We're in Seal Beach, and the work is remote, so your site can be hosted anywhere.

Only need the php2shell fix? The PHP patch page has the version table and where to look. Questions first? Email hi@jkca.studio.