Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
php2shell-lab — Black-box pentest lab for the PHP2Shell engine memory-corruption family (CVE-2026-109618 / CVE-2026-109619, CVSS 9.8/9.2). Dual-flag verified attack chain, agent-calibrated. EN/JP/ZH. | Kitploit
Tools/GitHubGitHub/taniungou/php2shell-lab
Container SecurityVulnerability AnalysisExploitationSecurity VirtualizationWeb SecurityCTFPenetration TestingLearning & EducationBinary ExploitationLabs & Practice
GitHub
823614 days agoNot yet reviewed
Share
taniungou/php2shell-lab

php2shell-lab

Black-box pentest lab for the PHP2Shell engine memory-corruption family (CVE-2026-109618 / CVE-2026-109619, CVSS 9.8/9.2). Dual-flag verified attack chain, agent-calibrated. EN/JP/ZH.

View Repository

php2shell-lab

English | 日本語 | 中文

Battle-tested: full solve verified by an AI pentest agent License: MIT

A black-box capture-the-flag target built around PHP2Shell — the 2026 PHP engine memory-corruption family (CVE-2026-109618 / CVE-2026-109619, CVSS 9.8/9.2, fixed in PHP 8.4.27). The vulnerability is in the engine, not the app: the tiny PHP application layer is intentionally clean of injections. You must fingerprint the runtime, correlate the advisory, and pick the right ballistics. Stuck? Black-box brief in CHALLENGE.md, full walkthrough in SOLUTION.md.

Quick start

Prerequisites: Docker Engine (or Docker Desktop on Windows/macOS) with Compose v2 — that's it. No PHP toolchain needed on the host. Works on Windows 10/11 (WSL2), Linux, and macOS; see the platform note below for which exploit chain your CPU supports.

git clone https://github.com/tani2shell/php2shell-lab.git
cd php2shell-lab
docker compose up -d --build          # first build pulls the pinned base image

Open http://localhost:18901 and sign in as user demo (password change-me-demo) to reach the app. From here the box is black-box: figure out the rest.

Want your own flag values and account passwords? Edit private.ini, then:

docker compose build \
  --build-arg FLAG_LOCAL=flag{...} \
  --build-arg FLAG_PROOF=flag{...}

Housekeeping:

./RESET.sh                            # one-command full reset (re-arms the leak window)
./teardown.sh                         # stop and free resources
docker compose logs -f                # watch the target

Flags are OverTheWire-style:

flagpathreadable by
local.txt/var/www/local.txtwww-data
proof.txt/root/proof.txtroot only

What makes it non-trivial

  • Engine-level, not app-level. No SQLi, no upload bypass puzzles. The box runs a PHP version inside the PHP2Shell affected range; everything else is your job.
  • Leaky by design, but only at first. The heap-disclosure primitive that matters has a narrow lifetime window after boot — most clones of this class of lab leave the door open forever; this one closes it (on purpose). Play it straight: hit the leak first, recon second — window time spent browsing is gone for good until the next up.
  • Two privilege paths to proof.txt with different elegance grades. At least one is live-fire verified; only one scales to a real fleet.
  • Calibrated by live fire. The full solve chain has been verified end-to-end by a local LLM agent across multiple attack rounds (per-round transcripts in SOLUTION.md). Full rating record and calibration data: DIFFICULTY.md.

Platform note (read this before filing an issue)

The public RCE-landing exploits for PHP2Shell assume an x86_64 kernel heap layout. On Apple Silicon (and other aarch64 hosts such as Windows-on-ARM) the leak primitives land but the RCE landing does not — we verified this across amd64-under-emulation, arm64-native, and the advisory authors' reference configuration (calif.io/php2shell, x86_64 Linux). On ARM hosts the intended solution is the disclosure chain, not the RCE chain — it works everywhere, including x86_64. Details: docs/PLATFORM-MATRIX.md.

Resources

  • 2 CPU / 1 GB RAM limit — safe to run next to other lab boxes.
  • No secrets from any real environment are baked in; all credentials are fake.

Solutions

Full kill chain, offsets, and per-round attack transcripts: SOLUTION.md — spoiler-protected by this section being at the bottom, promise.

License

MIT — build on it, fork it, use it in trainings (attribution appreciated).

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    696
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    499
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    396
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    340
  • 5

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    258
  • 6

    antifox

    antifox-ai/antifox

    AI multi-agent autonomous penetration testing platform that runs recon, attack-surface discovery, exploitation validation and evidence-backed report delivery.

    257

Explore all tools

Browse our collection of tools

View all tools →