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-check — Passive PHP2Shell (CVE-2026-109618, CVE-2026-109619) exposure checker with branded HTML reports. Single-file Python, no dependencies, no exploit payloads. | Kitploit
Tools/GitHubGitHub/completetech-security/php2shell-check
Defensive ToolsReconnaissanceVulnerability ScannersWeb Vulnerability ScannersVulnerability AnalysisScripting & AutomationInformation GatheringWeb Security
Share
GitHubcompletetech-security/php2shell-check

php2shell-check

Passive PHP2Shell (CVE-2026-109618, CVE-2026-109619) exposure checker with branded HTML reports. Single-file Python, no dependencies, no exploit payloads.

View RepositoryWebsite
434 days agoNot yet reviewed

php2shell-check by CompleteTech LLC

php2shell-check

Tests Release Python 3.10+ No dependencies AGPL-3.0 or commercial license

Passive triage for websites that advertise a PHP version affected by PHP2Shell
CVE-2026-109618 · CVE-2026-109619 · single-file, dependency-free


Overview

php2shell-check reads the PHP version a website already advertises in its public response headers and compares it with the official upstream fix for each PHP branch. It sends no exploit payloads, respects robots.txt, and reports uncertainty honestly: a hidden, conflicting or vendor-built version is unknown, never "safe".

  • Passive: one ordinary page request per target, after reading robots.txt, with verified TLS and a descriptive User-Agent.
  • Evidence, not proof: advertised versions are not verified runtime state. Every result records php2shell_exploitability=not_tested.
  • Offline-capable reports: CSV, JSON, or a self-contained HTML report. Interrupted runs can be rendered offline from a durable checkpoint.
  • Single file: wordpress_check.py uses only the Python standard library. The filename and default User-Agent are retained for compatibility; WordPress is not required for the PHP2Shell assessment.

[!IMPORTANT] Potential exposure is not confirmed exploitability. Headers cannot reveal the PHP SAPI, vendor backports, or real patch status. Treat every result as a prompt for an administrator to check. Check only websites you are authorized to assess.

Contents

  • Quick start
  • Interpreting results
  • What the checker requests
  • Usage
  • Reports, checkpoints and recovery
  • Report provenance
  • Limitations and responsible use
  • Agent skill
  • Documentation
  • Development
  • License

Quick start

Requires Python 3.10 or newer on Windows, macOS, or Linux. There is nothing to install: no pip package, API key, browser, or database. Use python3 where that is how Python is named on your system.

git clone https://github.com/CompleTetech-Security/php2shell-check.git
cd php2shell-check

python wordpress_check.py example.com                       # CSV to the terminal
python wordpress_check.py --input websites.txt --format html --output report.html

websites.txt is a text file with one authorized website per line; websites.example.txt shows the format using reserved example domains. See Usage for input rules and options.

Interpreting results

Every website result includes php2shell_status:

StatusMeaning
potentially_affectedA complete, unqualified PHP version below its branch's fix is advertised. Ask the administrator to verify.
fixed_version_reportedThe advertised version meets its branch's fix. This is a reported version, not a verified patch or clean bill of health.
unknownVersion hidden, partial, conflicting, pre-release, vendor-qualified, or outside the covered 8.2–8.5 branches.
PHP branch8.28.38.48.5
Fixed in8.2.358.3.368.4.278.5.12

Thresholds come from the PHP project's advisories for CVE-2026-109618 and CVE-2026-109619, checked on 2026-10-21. The table is embedded in the script and is not refreshed from the internet. Distributions such as Ubuntu backport fixes without changing the upstream version number, so packaged builds are always unknown.

Operational outcomes are separate from assessment results. A completed run can contain targets that were blocked, timed out, or out of scope; those rows have an unknown assessment, not a negative finding. See the full reference for the detection status and fetch_status values and every output field, and the assessment methodology for how each version is classified.

The HTML report

--format html produces a single offline file with your logo, summary tiles, and every result sorted by risk. It follows the reader's light or dark theme and prints cleanly.

Example PHP2Shell exposure report with the CompleteTech LLC logo

Synthetic example built from reserved example.* domains. View the HTML.

Use --logo path/to/logo.png and --brand "Your Company" to brand the report for your own organization. CSV and JSON remain available for spreadsheets and pipelines.

What the checker requests

  1. Normalizes and validates the supplied HTTP(S) URL.
  2. Reads the origin's /robots.txt and stops if the page is disallowed.
  3. Makes one ordinary GET request to the page, with verified TLS and an honest User-Agent.
  4. Inspects the X-Powered-By and Server headers, plus WordPress markers in the HTML already returned.
  5. Fetches nothing else: no linked scripts, admin pages, uploads, API endpoints, or crafted requests.

Redirect scope. Redirects stay within each supplied origin (scheme, hostname and effective port). Only same-host HTTP port 80 to HTTPS port 443 is implicitly allowed. Additional origins, including www names or different ports, require explicit authorization via repeatable --authorized-origin https://approved.example:8443. Page and robots redirects outside that scope stop before any destination request and report fetch_status=out_of_scope; robots permission is not authorization.

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.

    786
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

    506
  • 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.

    429
  • 4

    redforge

    cybersecurity91/redforge

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

    345
  • 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.

    262
  • 6

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    256

Explore all tools

Browse our collection of tools

View all tools →