exploit-validation

Exploit Validation

Purpose

Transform suspected vulnerabilities into confirmed findings through proof-of-concept (PoC) development and execution. Validate exploitability, measure actual impact, document exact reproduction steps, and produce definitive evidence. This skill bridges the gap between "this looks vulnerable" and "this is exploitable."

Triggers

• Bug bounty triage routes a suspected finding for validation
• High-confidence suspected vulnerability needs confirmation
• Code review identifies a vulnerability that needs runtime validation
• Chained vulnerabilities need end-to-end exploit demonstration
• Stakeholder requires proof of exploitability before remediation

Required Inputs

Input	Description	Required
governance_context	Active engagement governance record	Yes
finding	Suspected finding with preliminary evidence	Yes
target	Exact endpoint, function, or component to exploit	Yes
vuln_class	Vulnerability type (SQLi, XSS, IDOR, RCE, etc.)	Yes
access_level	Current authentication/authorization context	Yes
constraints	Any exploit restrictions (no data modification, rate limits, etc.)	Recommended

Workflow

1. Scope & Constraint Check — Verify:

   • Target is within authorized scope
   • Exploit type is within rules of engagement
   • Constraints from governance context are documented
   • Rollback plan exists for any state-changing exploit

2. Exploit Planning — Define:

   • Attack vector and payload strategy
   • Expected outcome if successful
   • Success/failure indicators
   • Potential side effects and mitigations
   • Required tools and environment setup

3. Payload Development — Build PoC:

   Injection Exploits (SQLi, XSS, CMDi, SSTI, etc.)

   • Start with detection payloads (tautologies, timing, error-based)
   • Escalate to extraction/execution payloads
   • Test WAF/filter bypass if initial payload blocked
   • Document each payload iteration and result