Autonomous PoC Validator

When to Run

• The user provides raw HTTP request data or a specific malicious payload and requests a target interface test.
• The user asks to "verify this PoC", "replay this request", "check for SQL exceptions", or "test for time/boolean blind injection".

Rules of Engagement (CRITICAL SAFETY GUARDRAILS)

Before executing ANY HTTP request via scripts/replay.py, you MUST adhere to the following safety protocols:

1. Explicit Confirmation: You must pause and ask the user for explicit authorization. For example: "⚠️ Please confirm you have authorization to test [Target URL]. Type 'yes' to proceed."
2. Do NOT Proceed: Do not execute the python script until the user explicitly replies with "yes", "y", or "proceed".
3. Target Scope: If the user asks to scan "the entire internet" or a large subnet, refuse the request. This tool is for single-target PoC verification only.

Workflow

1. Parse the target URL, Method, Headers (specifically Cookie and User-Agent), the Payload, and determine the required Encoding strategy (none, url, or base64).
2. Format the request data and pass it to the scripts/replay.py execution script.
   • Command execution example: python3 scripts/replay.py --url "{URL}" --method "{METHOD}" --data "{PAYLOAD}" --headers "{JSON_HEADERS}" --encode "{ENCODE}"
3. Parse the JSON output returned by the script (includes status code, elapsed time, content length, page title, redacted response_headers, and smart body snippet).
4. Perform deep analysis on the response context using the following dimensions:
   • Error-Based Check: Identify HTTP 500 Internal Server Error or anomalies. Scan the body_snippet for signature keywords like SQLSTATE, Syntax error, ExtractValue, XPATH syntax error, etc.
   • Time-Based Blind Check: Evaluate elapsed_seconds. If it closely matches or significantly exceeds the payload's injected sleep time (e.g., >= 5.0s), flag as a successful time-based injection.
   • Boolean Blind Check: Analyze content_length and page_title. Note any significant deviations from a normal baseline response (e.g., missing "Welcome" text, drastic size drop) indicating a boolean FALSE state.
5. Generate the final vulnerability validation report strictly adhering to the Output Format below.

Output Format

[+] PoC Validation Report

[] Target Interface : {Method} {URL}
[] Test Payload : {The critical injection code/payload}
[] Encoding Used : {none / url / base64}
[] Response Status: {Status Code}
[] Response Time : {elapsed_seconds}s
[] Content Length : {content_length} bytes

[!] Analysis Conclusion:
{Clearly state if the vulnerability exists. E.g., "Time-Based Blind SQLi confirmed. Response delayed by 5.12 seconds." or "SQL Error-Based Injection confirmed. Captured SQLSTATE[42000] exception."}

[-] Critical Evidence / Stack Trace:

{The extracted error logs, elapsed time evidence, or relevant response snippet demonstrating the vulnerability}