More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    PHP2Shell Fix for WordPress: Check, Patch, Verify

    1

    Reads your real PHP version, patches it in your hosting panel, and rechecks key pages.

    $19

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    PHP2Shell Fix for WordPress: Check, Patch, Verify

    PHP2Shell Fix for WordPress: Check, Patch, Verify

    Example session with this skill installed

    Is my WordPress affected by PHP2Shell? It's https://example.com, hosted on GoDaddy cPanel. I'm logged in to wp-admin and GoDaddy in Chrome.

    • Read your context and instructions
    • Compiled the php2shell fix

    Summary

    Verdict: PATCHED. Site Health shows PHP 8.3.35, which looks vulnerable (8.3 is fixed in 8.3.36). But GoDaddy Web Hosting runs CloudLinux and ships the fix as a backport

    with the same version number. Your PHP was built on

    21 Oct 2026, after the patch release, so the fix is in. No change needed.

    Based on a real run on 2026-10-22, with the site anonymized.

    What I checked

    StepResult
    AuthorizationYou confirmed you administer example.com and its hosting
    Outside check (no login)Apache · no Cloudflare · host bot challenge detected, so the baseline was taken in the browser instead
    Site Health → ServerPHP 8.3.35 · SAPI litespeed · WordPress 7.1.3
    Hosting panelcPanel → Select PHP Version: branch 8.3, selector locked by the host (no self-service switch)
    Host advisoryGoDaddy: Web Hosting patched 2026-10-22 13:30 UTC, "same version number, check build date"
    Build date21 Oct 2026, from the temporary probe GoDaddy's advisory recommends. You approved it. Random file name, live about 1.5 minutes, then deleted; its URL now returns 404
    Compromise check (read-only)3 admins, all known to you · Solid Security log: no unexpected logins or plugin changes since Oct 17 · host malware scanner: not available
    After-checkKey pages: same status codes and sizes as the baseline

    Report

    • Before → after: 8.3.35 (unclear) → 8.3.35 built 2026-10-21 (patched)
    • Changes: none to PHP. Temporary probe created and deleted (name and times in the report file).

    Still open: an old WordPress 4.7.3 entry under /wordpress in the GoDaddy dashboard (returns 404 from outside; ask GoDaddy whether files remain). Patching PHP doesn't remove an existing compromise; the basic check found no signs of one.

    Next steps

    1. Keep the report (php2shell-report.md) as evidence for your client.
    2. Ask GoDaddy to confirm that the /wordpress install is gone.
    3. Re-run this check if PHP announces a follow-up release.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    PHP2Shell (CVE-2026-109618 and CVE-2026-109619, CVSS 9.2) can let an unauthenticated attacker run code on servers with unpatched PHP in vulnerable configurations. Most WordPress sites run on PHP, and WordPress updates don't fix it: only a patched PHP does.

    Most guides stop at "update PHP". This skill walks the agent through doing it with you:

    1. Diagnose: reads the real PHP version and SAPI from wp-admin → Site Health, in English or Spanish admin. It doesn't guess from headers. mod_php is flagged as the highest risk.
    2. Check for an earlier compromise: a read-only look for unknown admins and for your security plugin's or host's scanner alerts. Patching doesn't remove a backdoor, and the skill says so.
    3. Decide: patched, vulnerable or unclear, against the first fixed version of your branch (8.5.12, 8.4.27, 8.3.36 or 8.2.35). It also knows that CloudLinux hosts such as GoDaddy patch without changing the version number, so it checks the build date before calling a site vulnerable.
    4. Patch or escalate:
      • If your panel offers a patched build, it switches to it after telling you exactly what changes and how to undo it.
      • A branch change requires a backup and a compatibility check first: .htaccess php_value lines, CloudLinux extensions, addon domains.
      • If your host hasn't shipped the fix yet, you get a ready-to-send support ticket in English or Spanish.
      • Includes step-by-step guidance for cPanel (MultiPHP and Select PHP Version), Hostinger hPanel, Plesk and SiteGround Site Tools.
    5. Mitigate: if you can't patch today, it checks your Cloudflare PHP2Shell rules and tells you what does and doesn't help. Spoiler: .user.ini doesn't.
    6. Verify: compares the status and size of your key pages before and after, from outside, with cache busting. It detects hosting bot challenges that would make those checks lie. You get a one-page report.

    You stay in control. The skill tells the agent never to type your passwords or 2FA codes, to ask for your explicit yes before every change, backup or download, never to run or download exploits, and not to create files on your server. The one exception is a one-line build-date check, used only when your host's advisory recommends it and you approve. It's deleted right away and confirmed gone.

    Tested on a real site. On 2026-10-22 the skill ran end to end on a live school WordPress on GoDaddy cPanel hosting. Site Health showed PHP 8.3.35, which looks vulnerable. The skill went on to check the build date (21 Oct 2026, a CloudLinux backport) and correctly reported the site as patched. It also checked for signs of an earlier compromise and verified the site from outside, through the host's bot challenge. Everything that run taught it is now in the skill.

    Bilingual: it talks to you in your language. Report and support-ticket templates in English and Spanish.

    Known limitations

    • Managed WordPress hosts (Kinsta, WP Engine, WordPress.com…) rarely let you choose the PHP patch level. There you get a ticket, not a fix.
    • Many shared hosts only let you choose a branch, and the patch level depends on the host's packages.
    • Hostinger hPanel can't downgrade PHP, so the skill treats that change as irreversible.
    • On CloudLinux hosts without SSH, confirming the build date may require asking the host (the skill drafts the question).
    • The compromise check is basic. It's not a malware scan.
    • Panel menus change. The skill finds controls by their text, but an unusual panel may need your help.
    • The facts are dated 2026-10-22. On every run the skill re-checks php.net.

    Changelog

    • 1.0.0 (2026-10-22): first release.

    Cannot handle credentials or 2FA. Does not perform malware removal. Requires user to manually trigger backups. Build-date probes require explicit host advisory alignment.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 25 days ago

    Requires

    Claude in Chrome or another browser tool

    Permissions

    Terminal / Shell
    Network Access
    Read Files
    Write Files
    Browser

    Browser: drives your own Chrome through wp-admin and your hosting panel; you log in yourself, and every change needs your explicit yes. Terminal + network: scripts/external-check.sh sends plain GET requests only to the site URL you pass (and its http/https redirects). Advisory pages read in the browser: php.net, rapid7.com, tenable.com, cisa.gov, blog.cloudflare.com, sansec.io, codeable.io, therepository.email, aws.amazon.com, hostinger.com, godaddy.com, support.plesk.com, plesk.com, docs.cpanel.net, siteground.com. Write files: only to save the report if you ask. No environment variables, no data sent anywhere else.

    Listed25 days ago

    What's inside

    Frequently Asked Questions

    No. The bug is in PHP itself. The WordPress security team has said no WordPress update is needed or planned. Only a patched PHP (8.3.36, 8.4.27, 8.5.12, 8.2.35 or a host backport) fixes it.

    Not necessarily. On CloudLinux hosts like GoDaddy Web Hosting the fix is a backport that keeps the old version number; only the build date changes. The skill checks the build date before calling a site vulnerable.

    The skill checks what your site actually runs against the host's claim, and gives you a dated report as evidence. If they don't match, it drafts the support ticket for you.

    The skill requires the agent to ask first, with the rollback spelled out, and to take a backup before any branch change (e.g. 8.3 to 8.4) or any change the panel can't undo. You type your own passwords and 2FA codes.

    Patching PHP doesn't remove a backdoor. The skill runs a basic read-only check (unknown admins, security plugin logs, host scanner) and tells you plainly if you need incident response. It doesn't clean malware.

    Partly. On a VPS it tells you which packages to update and how to confirm the backport, but it won't run commands on your server. Without a browser tool, the outside check and the step-by-step guidance still work; you do the clicking.

    New in Security