> jenk.com.au/free/php // free check

Is your website open to the PHP bug?

Two critical bugs in PHP, the code behind WordPress and about 7 in 10 websites, let a stranger take over a web server without a password. The fix came out on 21 October. Type your website and we'll check if it's at risk, then show you how to fix it.

php2shell check

    We only look at what your site shows any visitor, the same as a web browser. We never attack it or test the bug.

    00What happened

    On 21 October the PHP team fixed two bugs it rated critical (9.2 out of 10). They're called PHP2Shell (CVE-2026-109618 and CVE-2026-109619). In plain English: if PHP runs out of memory at the wrong moment, or leaves old data lying around between visitors, an attacker can use that mess to run their own code on the server. No login needed. Everything on that server is then up for grabs: your site, its database, customer details, and any emails or passwords stored there.

    Attackers moved fast. Amazon's security team saw someone trying it on 17 October, four days before it went public. US cyber agencies say that if you can't update, take PHP sites offline until you can, and the Australian Cyber Security Centre has a critical alert out.

    Your PHP versionFixed in
    8.58.5.12 or newer
    8.48.4.27 or newer
    8.38.3.36 or newer
    8.28.2.35 or newer (8.2 stops getting fixes on 31 Dec 2026)
    8.1 or olderNo official fix. Move to 8.3 or newer.

    Not on WordPress or PHP at all? Shopify, Wix, Squarespace, Webflow and most site builders don't run your site on PHP you have to patch. You can skip to the account checks.

    01Check which PHP version your site runs

    Pick whichever is easiest. You're looking for a number like 8.3.36.

    Then compare it with the table above. If the number has extra bits on the end, like 8.1.2-1ubuntu2.19, your Linux vendor builds PHP and may have patched it without changing the main number. Your host or developer can confirm.

    message to your host or developer

    Hi, I'm checking my website for the PHP security bugs fixed on 21 October 2026 (PHP2Shell: CVE-2026-109618 and CVE-2026-109619). Can you please confirm:
    
    1. Which PHP version my site runs, and that it has these fixes (8.2.35, 8.3.36, 8.4.27, 8.5.12 or newer, or a patched build from your Linux vendor)?
    2. That PHP was restarted after the update?
    3. If my site is on PHP 8.1 or older, what you recommend to move it to a supported version?
    
    Thanks!

    02On normal web hosting

    This is most small business sites: you pay a host like VentraIP, Crazy Domains, Hostinger, SiteGround or GoDaddy and log in to a dashboard such as cPanel or Plesk. On this kind of hosting the host installs PHP updates on its servers. Your job is to make sure your site isn't stuck on an old version, and that they've done theirs.

    03On managed WordPress hosting

    Hosts like WP Engine, Kinsta, Flywheel, Pantheon and WordPress.com run the servers for you, so they install the PHP fix themselves. Two things are still on you:

    04On your own server

    If your site runs on a server you or your developer manage (a VPS or cloud server at AWS, DigitalOcean, Vultr, BinaryLane and so on), nobody else is going to patch it. Send this section to whoever looks after it.

    Ubuntu or Debian

    terminal

    sudo apt update && sudo apt upgrade
    # shows which PHP packages contain the fix (no output = not fixed yet)
    zgrep -l "CVE-2026-109618" /usr/share/doc/php*/changelog.Debian.gz
    # restart PHP so the fix is actually loaded
    sudo systemctl restart 'php*-fpm'
    # only if you use Apache with mod_php
    sudo systemctl restart apache2

    Red Hat, AlmaLinux, Rocky or Fedora

    terminal

    sudo dnf upgrade 'php*'
    rpm -q --changelog php-common | grep CVE-2026-109618
    sudo systemctl restart php-fpm
    # only if you use Apache with mod_php
    sudo systemctl restart httpd

    Docker

    Pull the latest image for your PHP tag (for example php:8.3-fpm), rebuild your image and redeploy. Then check the version inside the container:

    terminal

    docker run --rm php:8.3-fpm php -v

    Built PHP yourself, or on Windows? Get the fixed release from php.net/downloads. Either way, check the version your website uses (WordPress Site Health, or php-fpm8.3 -v), not just php -v in the terminal. They can be different.

    05PHP 8.1 or older

    PHP stopped updating 8.1 and older, so there's no official fix. Some hosts and Linux vendors patch old versions themselves, so ask yours. The real fix is moving to PHP 8.3 or newer. For a WordPress site:

    1. Back up the site and database. Most hosts have a backup button.
    2. Update WordPress, your theme and every plugin first. Old plugins are what usually breaks on a newer PHP.
    3. Try PHP 8.3 on a staging copy if your host offers one. If not, switch the live site at a quiet time.
    4. Click through the site: home page, contact form, bookings, checkout. If something breaks, switch back and call a developer, but remember the old version is still exposed while you wait.

    If you can't get off the old version soon, US cyber agencies (CISA and the FBI) say to take the site offline until you can. At the very least, do the stopgap below today.

    06Can't update today?

    These buy time. None of them is the fix.

    php.ini (then restart every PHP worker)

    session.upload_progress.enabled = 0
    post_max_size = 8M    ; or 32M if your site takes file uploads

    Set these in php.ini or the FPM pool, not in .user.ini or with ini_set(). PHP's advisory has the full list, including a memory_limit change with trade-offs to read first.

    07After you update

    Attacks started on 17 October, so if your site was open before you patched, spend ten minutes checking nobody got in.

    Hide your PHP version

    If our check could read your PHP version, so can every attacker's scanner. Turn it off with expose_php = Off in php.ini (on normal hosting, ask your host). It doesn't fix anything, but it stops you being an easy match.

    08Not sure what your site runs on?

    If someone built it for you, send them the message above. If it turns out to be WordPress or anything PHP, follow the steps for your hosting. If it's a site builder like Shopify, Wix or Squarespace, you're fine on this one.

    09For everyone: two account checks

    Bugs like this one leak passwords, and leaked passwords get tried everywhere. Even if your site is fine:

    What this check can't tell you

    10Sources

    Got this from a reel? Every reel on @jenkk.ai ends with a word to comment, and the next freebie is on its way. No affiliate links on this page.

    Follow @jenkk.ai