shulkwisec
Series6 writeups/ updated 2026-11-14

PHP to Shell

Three bugs account for almost every “PHP app to shell” story that has ever been written up: an upload endpoint that doesn’t check what it’s given, an include() call that trusts its argument, and an unserialize() call that trusts its input. Everything else — the specific CVE, the specific framework, the specific webshell — is a variation on one of those three.

This series works through each one from the mechanism up: what has to be true for it to fire, what a hardened config does to kill it, and what it looks like on the wire when it works. Where I could build a safe, fully isolated lab for a technique, I ran it and the post says so. Where I couldn’t — a Windows-only trick, a vector needing a PHP extension I didn’t have installed — the post says that too, instead of quietly reading the same either way.

  1. Building an isolated lab worth trusting
  2. Unrestricted upload to webshell
  3. File inclusion to code execution
  4. PHP object injection to code execution
  5. The CVEs that carry this chain in the wild
  6. Webshell payloads, and how they get caught

Writing